| 996 | | The experiment interface controls managing experiment definitions and realizing experimnets (allocating and initializing resources). The experimnet definition is in some flux, which is reflected in this section. |
| | 996 | The experiment interface controls managing experiment definitions and realizing experiments (allocating and initializing resources). The experiment definition is in some flux, which is reflected in this section. |
| | 997 | |
| | 998 | An experiment is a collection of aspects, each of which controls part of the experiment's environment and operation. Some aspects are understood directly by the testbed, while others are interpreted and accessed by tolls inside the experiment. Such tools may be written by DETER administrators or by experimenters themselves. |
| | 999 | |
| | 1000 | An [http://www.isi.edu/~faber/tmp/DeterAPI/doc/net/deterlab/testbed/api/ExperimentAspect.html aspect] is a named and typed object associated with the the experiment. Specifically, an aspect has the following attributes: |
| | 1001 | |
| | 1002 | name:: |
| | 1003 | A unique string scoped by aspect type used to identify the aspect instance |
| | 1004 | type:: |
| | 1005 | A string that tells the testbed or tool how to interpret the aspect. The current interface interprets '''topology''' aspects as an experiment layout, and treats the rest as opaque. |
| | 1006 | subtype:: |
| | 1007 | A string characterizing the aspect further. Subtypes may be created by the testbed or tools. |
| | 1008 | data:: |
| | 1009 | The contents of the aspect. This will be empty if datareference has a value |
| | 1010 | datareference:: |
| | 1011 | A URI that points to the contents of this aspect |
| | 1012 | readOnly:: |
| | 1013 | A boolean, true if the aspect can be modified. |
| | 1014 | |
| | 1015 | [http://www.isi.edu/~faber/tmp/DeterAPI/doc/net/deterlab/testbed/api/Experiments.html experiments javadoc] |
