Ginpex/Metamodel
Control Flow Tasks
Name | Symbol | Activity Diagram Syntax | Description | Attributes |
---|---|---|---|---|
SequenceTask | Executes multiple nested task in a sequence. Nested tasks are ordered; a nested task is being executed once its predecessor task has been completed. | nestedTasks: An ordered list of nested tasks. | ||
ParallelTask | / | Executes multiple nested task in parallel. | nestedTasks: A list of nested tasks.
boolean stopAfterFirstTaskCompleted: Indicates whether the ParallelTask should stop once the first nested task has completed. Otherwise, the ParallelTask waits until all nested tasks have completed. | |
LoopTask | Executes a nested task multiple times. | nestedTask: The nested task which has to be executed in a loop.
stopCondition: The stop condition is specified by one of the following model elements: | ||
MachineTaskSet | Executes a set of tasks on a specified machine. | nestedTask: The root task to be executed on the machine.
MachineReference targetMachine: The machine on which the nested task is to be executed. MachineReference calibrationFilesFromDifferentMachine: If specified, nested task uses calibration files from this machine, instead of the calibration files from the target machine. | ||
ForkTask | / | Executes a nested task in a newly forked thread or process. | task: The nested task which has to be executed in a new process.
boolean waitForTheTaskToFinish: Indicates whether the ForkTask waits for the nested task to complete before completing himself. boolean useProcessInsteadOfThread: Indicates whether the task should execute the nested task in a child OS processes. If set to false (default), a thread is used. | |
DynamicMachineTaskSet | Datei:DynamicMachineTaskSetActivityDiagram.png | Allows for Load Driver to dynamically register with the controller machine to receive tasks for execution. | nestedTask: The root task to be executed on a load driver once he registers.
MachineReference calibrationFilesFromDifferentMachine: If specified, nested task uses calibration files from this machine, instead of the calibration files from the target machine. Not supported yet. |
Resource Demand Tasks
Additional Tasks
Name | Symbol | Description | Attributes |
---|---|---|---|
StatusTask | Report the experiment status to the controller. This task can for example be used to report on the progress during long-running experiments. | ||
ExecuteLibraryTask | Execute task logic that is provided by a jar library. This allows for executing task logic without extending the metamodel or code-generation templates. For more details, see Using external libraries for generating load | libraryPath: Absolute path to the jar file on the controller machine. The jar file will be transferred to the Load Driver for execution.
className: The fully qualified class name which provides the task logic implementation. | |
WaitTask | Do nothing for the specified duration. | duration: The wait duration in milliseconds. |
Distributions
Sensors
Sensors are specified by means of the ProbeSpec metamodel. Editor shortcuts exist for convenient sensor creation and deletion.