ifference between revisions of "EMK:Schedules"
Jump to navigation
Jump to search
(Created page with "{{#hidens:}} Back to User Manual Main Page") |
|||
| Line 1: | Line 1: | ||
{{#hidens:}} | {{#hidens:}} | ||
| + | [[File:Schedule.jpg|400px|thumb|right|Example Schedule Window]] | ||
| + | Schedules are designed to give advanced control over various aspects of a Run during its execution. This is achieved by changing how values for EMarket's internal variables are derived. In other words the Schedule extends and modifies EMarket's underlying scripting language which describes the input parameters at each Tick of a Run. In this regard a Schedule can be considered analogous to programming language for EMarket. | ||
| + | The Schedule can be used to define: | ||
| + | *variables | ||
| + | *the traits of entities | ||
| + | When a variable is defined, a new value is added to the run data, based on the definition. When a trait is defined through the Schedule, the entity and trait concerned will already exist in the model, but the existing definition of the trait's value will be modified. | ||
[[EMK:EMarket User Manual | Back to User Manual Main Page]] | [[EMK:EMarket User Manual | Back to User Manual Main Page]] | ||
Revision as of 12:06, 12 November 2012
Schedules are designed to give advanced control over various aspects of a Run during its execution. This is achieved by changing how values for EMarket's internal variables are derived. In other words the Schedule extends and modifies EMarket's underlying scripting language which describes the input parameters at each Tick of a Run. In this regard a Schedule can be considered analogous to programming language for EMarket.
The Schedule can be used to define:
- variables
- the traits of entities
When a variable is defined, a new value is added to the run data, based on the definition. When a trait is defined through the Schedule, the entity and trait concerned will already exist in the model, but the existing definition of the trait's value will be modified.