error-message
success-message
saving-message
warning-message
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
A workflow describes how a collection of objects interact. Generally, it denotes a path from some input to some eventual result. For instance, you can describe a flow from a benchmark to a simulator. To do this, you would first attach a simulator. At that point, it will show you the possible input objects you can attach. You can select a benchmark on the left-hand side and all runs will use that benchmark with the given simulator.
Use ranged and listed options to create a set of experiments.
Type 1, 2, 8
in a field to say you wish to run a separate experiment for each of the listed options.
Type 1 ... 4
in a field to sweep an option and create an experiment for each valid value in that range.
If you would like to created a range with a step, use the following syntax to add a mathematical function to update the next value based on the previous value. For instance, for a range that represents all even values use:
0 ... 20 : x+2
and it will step every 2 values.
You can express other complex values like so:
1 ... 20: x*2
for powers of two: 1, 2, 4, 8, 16.
Notice that x
in each example will be the previous value before generating the next until x is greater than the bounds of the range. In this case, 20
.
You may combine these into a variety of ways. For example: 1 ... 9 : x+3, 21, 121
will create experiments for 1
, 4
, 7
, 21
, and 121
.
All permutations of configurations will result in new experiment runs.
Click on the 'configuration' button on a node in the workflow.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
This page lists the published changes made to the object.
When you are editing the object, it will be in a special view called a stage. In this mode, edits can be made but are not publicly visible until they are published when a snapshot is made.
The Activity tab lists these snapshots and the changes made to the object.
Whenever you wish to create a snapshot that can be used by the public, you use the Publish button. You can then supply a message that indicates what changes have been made.
The Versions tab lists the named snapshots of the artifact. These are specific points in time given a meaningful and typically ordered name. That is, a version might be "1.0" for the first stable release of some software or a dataset. The next might then be "2.0".
This tab lists the known named versions and the actors that named them. These versions are verified by the system as having been performed at the provided time by the given actor. This is done through a cryptographic key signing process.
Author: wilkie <wilkie05@gmail.com>
Makes the experiment object its own workflow object.
Author: wilkie <wilkie05@gmail.com>
Adds basic experiment data.
Author: occam <occam@occam.cs.pitt.edu>
adds Occam Core Repository as author
Author: occam <occam@occam.cs.pitt.edu>
Created experiment Blank Experiment
Name | Revision | Signed By | Signed On |
---|
No Version Tags
Confirm message?