Changes between Version 32 and Version 33 of GeniExperiments
- Timestamp:
- 03/26/13 11:43:46 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniExperiments
v32 v33 4 4 = GENI Experiment Workflows = 5 5 6 Last edited on 032 513 by HEM6 Last edited on 032613 by HEM 7 7 8 8 … … 24 24 25 25 g) Experimenter prototypes a service, without opt-in users 26 26 27 27 h) Experimenter prototypes a service, with opt-in users 28 28 … … 65 65 66 66 67 == 4) BasicGENI Experiment/Tutorial/Test Workflow (Harry) ==68 69 Start with one " BasicGENI Experiment/Tutorial/Test Workflow", and later introduce variations that cover additional types of experiments67 == 4) Type 1 (Basic) GENI Experiment/Tutorial/Test Workflow (Harry) == 68 69 Start with one "Type 1 (Basic) GENI Experiment/Tutorial/Test Workflow", and later introduce variations that cover additional types of experiments 70 70 71 71 === 4.1) Uses === … … 92 92 93 93 a) Includes eight steps that are self-contained, which allows for all the variations in flow that occur in a real experiment: repeating steps (e.g., many runs); re-ordering steps (e.g., analyzing much later); skipping steps (e.g., do not archive) 94 95 + Step 1: Design experiment, and find or wirte necessary software, rspecs and/or scripts 96 97 + Step 2: Establish experiment management environment 98 99 + Step 3: Obtain slice of GENI resources, and then install I&M and experiment software 100 101 + Step 4: Configure and initialize I&M and experiment services 102 103 + Step 5: Run and orchestrate I&M and experiment services, to complete run of experiment 104 105 + Step 6: Analyze experiment results, and decide on next step(s) 106 107 + Step 7: When no longer needed, release all experiment resources 108 109 + Step 8: Optionally, archive selected measurements and/or experiment artifacts 94 110 95 111 b) Each step typically includes these items: … … 178 194 p) Suggested production methods are: 179 195 180 + TBD196 + Currently done with wiki, but it would be helpful to find an easier method 181 197 182 198 === 5.2) Customized Document, Including Parameters, Annotations and/or Results === … … 212 228 f) Suggested production methods are: 213 229 214 + TBD215 216 === 5.3) AdditionalOne-Page Summary Document ===217 218 a) To supplement a document on a web page, particularly for an in-person tutorial230 + Could this be based on approach used in Lab wiki? 231 232 === 5.3) One-Page Summary Document === 233 234 a) To supplement a document on a web page, typically for an in-person tutorial 219 235 220 236 b) Provide a one-page summary on paper, that: … … 224 240 + allows them to easily check off steps, and 225 241 226 + capture simple notes and results.242 + capture simple notes and basic results. 227 243 228 244 229 245 c) Suggested production methods are: 230 246 231 + TBD247 + Abstract on-lin document, and use pdf to produce one-page document 232 248 233 249 === 5.4) Dual-screen Presentation, of Workflow Steps and Current Console/Browser === 234 250 235 a) First screen shows workflow steps, e.g., a browser pointed at wiki holding steps 236 237 b) Second screen shows current console/browser, as instructor follows the steps. 238 239 c) This avoids having to go back and forth, if there were only one screen, and makes it easy for the student to follow along. 240 241 242 === 5.5) Additional Video "Document" === 251 a) To improve the presentation at an in-person tutorial 252 253 b) First screen shows workflow steps, e.g., a browser pointed at wiki holding steps 254 255 c) Second screen shows current console/browser, as instructor follows the steps. 256 257 d) This avoids having to go back and forth, if there were only one screen, and makes it easy for the student to follow along. 258 259 260 === 5.5) Short Video that Describes One or More Steps === 243 261 244 262 a) To supplement a document on a web page, for an in-person tutorial, or for use as an off-line tutorial 245 263 246 b) Provide a short video, that summarizes how to complete one or more steps.264 b) Provide a short video, that describes how to complete one or more steps. 247 265 248 266 c) An example is the video included in the GIMI tutorial at GEC16 (ref) … … 250 268 d) Suggested production methods are: 251 269 252 + TBD270 + Mike Zink can suggest a method. 253 271 254 272 … … 278 296 b) Required functions: 279 297 280 + Availability of artifacts in archive from a referenceexperiment/tutorial/test298 + Availability of artifacts from a reference experiment/tutorial/test, that can be copied over for a new experiment/tutorial/test 281 299 282 300 + Scratchpad, for transfer of artifacts between tools, operating in different steps 283 301 284 + Storage of artifacts after an experiment is finished, for later analysis or repetition302 + Storage of artifacts after an experiment/tutorial/test is finished, for later analysis or to repeat the experiment/tutorial/test 285 303 286 304 + Accessible from all services owned (or acting for) the user … … 288 306 c) Design of GENI Storage and Archive Service: 289 307 290 + Being built to provide a place for all such artifact, including descriptors 308 + Being built to provide a place for all such artifacts 309 310 + Follows a well-defined structure, with well-defined descriptors (metadata) 291 311 292 312 + iRODS ref … … 317 337 318 338 a) Issue: variations with type of users (novice to expert) and thus interfaces (graphical to script); can these be mixed? 319 339 320 340 b) Issue: variations between InstaGENI and ExoGENI, between GIMI and GEMINI; is there a common set? 321 341 322 342 c) Issue: variations from this basic workflow, to more-specialized workflows; which should be considered? 323 343