[[PageOutline]]


= 4.2)  I&M Use Cases for Experiments, and Support for Experimenters =

==  4.2.1)  Goals ==

  Provide a concise but complete definition of I&M Use Cases for Experiments.  Include the support that should be available to experimenters, i.e., on-line instructions, examples and help desks.  [[BR]]

== 4.2.2)  Team ==
 
  CO-LEAD  Jim Griffioen (U Kentucky)  [[BR]]
  CO-LEAD  Mike Zink (UMass Amherst)  [[BR]]
  Max Ott (NICTA)  [[BR]]
  Prasad Calyam (Ohio Super Center)   [[BR]]
  Harry Mussman  (GPO) [[BR]]

== 4.2.3)  Meetings ==

== 4.2.4)  Vision ==

 Towards Max Ott's vision for experiment support  [[BR]]

[http://groups.geni.net/geni/attachment/wiki/GEC12InstMeasWorkingSession/Will%20RSpec%20help%20us%20to%20do%20better%20science%20-%20GEC11%20-%20July%202011.pdf  slides] [[BR]]

== 4.3.5)  Basic experiment use case ==

 Basic experiment use case:  [[BR]]

 1)  Setup and run experiment using Experiment Control Tools and Experiment Orchestration Service  [[BR]]
 1b)  Include resources and software for instrumentation and measurement services in the slice    [[BR]]

 2)  Setup and run measurement services within slice, using persistent services as necessary.    [[BR]]

 2b)  Option:  get measurement data from persistent MP.   [[BR]]
 3)  Gather MD into MAP service, to analyze and.or visualize, during or after experiment; formulate MDOD.  [[BR]]
 4)  Archive MD with MDOD.  [[BR]]
 5)  Share archived MD with others, per policy included within MDOD.    [[BR]]
 6)  Pull MD out of archive, to analyze and/or visualize.  [[BR]]
 

d)  Extended experiment use cases:  [[BR]]
  1)  WiMAX site measurement
  2)  LEARN/BEN layer 0,1 or 2 real-time measurements
  3)  Sensor network (radars, power monitors)
  4)  Measure DiCloud workflow
c)  What support must be provided for Experimenters?  how?  [[BR]]