Version 8 (modified by, 10 years ago) (diff)


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.

4.2.2) Team

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

4.2.3) Meetings

4.2.4) Vision

Towards Max Ott's vision for experiment support


4.2.5) Basic experiment use case

Basic experiment use case:

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

2) Setup and run measurement services within slice, using persistent services as necessary.
2b) Option: get measurement data from persistent MP.

3) Gather MD into MAP service, to analyze and.or visualize, during or after experiment; formulate MDOD.

4) Archive MD with MDOD.

5) Share archived MD with others, per policy included within MDOD.

6) Pull MD out of archive, to analyze and/or visualize.

4.2.6) Extended experiment use cases

Extended experiment use cases:

a) WiMAX site measurement

b) LEARN/BEN layer 0,1 or 2 real-time measurements

c) Sensor network (radars, power monitors)

In this case, the measurements are at the heart of the experiment

d) Measure DiCloud workflow

4.2.7) Basic host measurements

4.2.8) Support for experimenters

c) What support must be provided for Experimenters? how?


Attachments (1)

Download all attachments as: .zip