Besides visualizer output, we need some output that is geared more towards the internal functionality of the system. We call this ``events output''. The name means that events output is triggered by some event. Typical events are vehicle departure, vehicle arrival, or link traversal.
Specifically, our events file consists of the following fields. From now on, we deviate from Transims formats and use our own formats. The main reason is that the remaining files are not very large and thus converting them when necessary seems justified. As argued elsewhere, in the longer run these files should all be in XML format. events
These events will be needed later when we introduce feedback and learning.