This file documents the gRMA task editor. The gRMA task editor provides an interface to specifying the details of a single task in a real time system.
NOTE: The gRMA system is capable of specifying a system which the current analyzer cannot produce results for. This is due to gRMA being in an early state of development. Please consider contributing to the project to address gaps as you find them.
This field specifies the name of the task.
This field allows you to specify the nature of this task.
Periodic
this task is run at predictable intervals. Its interval is specified in the period field.
Bounded
a non-periodic task that is garaunteed to not be run more frequently that the value specified in the period field. This allows us to treat the task as Periodic.
Bursty
A non-peridoc task that can run arbitrarily soon after a previous event. In this case the period field should contain two values separated by a comma. The first is the burst interval - that is the minimum time between 'bursts'. The second is the maximum burst size - that is the maximum number of events that can arrive in a single 'burst'.
Irregular
a non-peridoc task whose arrival pattern is not regular but is known to follow some deterministic function. In this case the function should be specified in the period field. When support is added to the analyzer for this type of task the format of the function will be given here.
Unbounded
a non-peridoc task whose arrival pattern is not regular but is known to follow some probablistic function. In this case the function should be specified in the period field. When support is added to the analyzer for this type of task the format of the function will be given here.
See above for the various meanings of the period field.
The maximum time that this task can take. You must include the time using any resources that you assign un the Resource Usage screen.
The time that this task MUST complete by, relative to the start of each run. The value of 0 is special - it means that the deadline is at the end of the period. Deadlines may be any value - inside or outside the period.
The priority of the task. Lower numbers are 'higher' priorities. Rate monotonic analysis models the behaviour of fixed-piority systems, and as such each task must be assigned a distinct priority.