Simulation event scheduling and dispatching engine

Registered by Mike Allen on 2007-04-03

The simulation engine consists of two primary classes and their derivations: a Simulation singleton class that controls the execution of the simulation, and an abstract Event class that represents individual events and their actions. (The EventQueue class mentioned in the original specification has been deferred.)

Events can be scheduled, and then subsequently get dispatched, but they currently cannot be descheduled or rescheduled. Events are dispatched in order of their due time and priority.

Blueprint information

Status:
Started
Approver:
Mike Allen
Priority:
Essential
Drafter:
Mike Allen
Direction:
Approved
Assignee:
Mike Allen
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Good progress
Milestone target:
None
Started by
Mike Allen on 2011-08-31

Related branches

Sprints

Whiteboard

2011-08-31:

Re-writing Facsimile in Scala. New simulation event engine being coded.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.