Life History Events
HexSim Event Basics
Each HexSim event has a unique purpose, interface, and requisite parameters. Two things that most events do have in common are their Output and Description tabs. Output tabs are used to control what data an event writes to the simulation log file. Since log files may become quite large, there can be value in not recording the output from some processes.
Event logging is always on by default. Simulation-wide logging can also be delayed or turned off for an entire simulation. If any part of logging is turned off, a yellow exclamation point icon will be placed to the right of the event type, in the main window's Event Sequence. There is one exception to this rule: in Census events, the logging of genomes is off by default, and this does not cause the icon to be displayed. The description tabs allow users to record notes, which will then be stored in the scenario XML file.
Event's description tabs are provided so that users may place notes directly into the models they develop.
HexSim includes an extensive validation scheme that attempts to flag invalid parameter values. In most cases, invalid parameters and events will be identified with a red exclamation point icon. Also, a tool-tip (a small message window) will pop up when the mouse is placed over the red exclamation point. These tool-tips can be valuable debugging aids.
All of the basic operations that act on events can be accessed through the event context menu (obtained by right-clicking). This context menu has options for event creation, editing, copying, renaming, and deletion. The context menu also provides access to event coloring, triggering, and some display parameters.
Each HexSim event can be assigned a color. This is done using tools available in the event context menu. Coloring events can add clarity to the life cycle structure. Automatically generated events will be colored black (when added by population creation) or gray (when added by trait builders), but these colors can be changed.
Event triggers can be used to make events active for just a subset of the simulation time steps. Events may trigger once, or during a period defined by a starting and ending time step. In the latter case, a periodicity setting is also available. For example, suppose an event starts at time step 5, has a period of 3, and triggers for just 1 time step per period. The event will then execute on time steps 5, 8, 11, 14, etc. An event that starts at time step 5 and has a period of 10 will execute on time steps 5, 15, 25, 35, etc. If the time step is a day, and an event starts on step 150, triggers with period 365, and triggers for 30 time steps per period, then the event will fire for a month each year, beginning on the 150 day of the year.
When triggering is set, an icon will be displayed in the event sequence, just to the left of the event. A single-arrow icon is used if the event triggers just once, and a double-arrow icon indicates that an event will trigger more than once. The arrow icons will turn red if triggering scheme becomes corrupted. The triggering conditions will be displayed in a tool-tip when the mouse is placed over a triggering icon. When triggering is off, events will be active in every time step. In addition to the context menu, the triggering dialog can be accessed by double-clicking the triggering icons.
Events can also be turned off entirely by selecting the Toggle Event On/Off context-menu option.