Features

khronos engine

Hierarchic model structure. Two major base components: Component (atomic) and Model (composite).
Event and process-based simulation approaches supported.
Basic event scheduling. Run function f at time t.
Advanced inter-component synchronization mechanisms (signals and triggers). Run function f if component c emitted signal s.
Automatic data collection facilities (based on composite conditions). Run a collection routine cr when condition c occurs.
Native action reneging support.
Allows building complex composite conditions combining simple conditions with python operators, e.g. c3 = c1 & ~c2 (c1 and not c2)
Action interrupts and component passivation/activation.
Pause/stop/resume possible on atomic and composite components.
Pause/stop/resume applied to data collection, i.e. pause, stop, or resume data collection on a given component or model.
Customizable simulation tracing (useful for debugging) and categorized logging.
Real valued action prioritization mechanism allows an infinite range of priority values to order simultaneous events or triggers.
Optional Signal and Trigger type checking.
Multi-run support.
Per component initial configuration.
Provides a set of predefined generic components (Queue, Creator, Destructor, Router, Dispatcher, Resource).

Currently predefined components exist for