
Event types and order in which they are thrown.
The following types of events are currently supported and should be generated by a mobility simulation:
| id | name | data | description |
| 0 | arrival | time, agent-id, link-id | An agent arrives at a link at the specified time |
| 2 | left link | time, agent-id, link-id | An agent leaves a link at the specified time. This builds a group together with 5-entered link. An agent moves through the network by entering and leaving link until it reaches its destination link. |
| 3 | stuckAndAbort | time, agent-id | Used for deadlock-prevention. If a deadlock occurs at some place, we solve it be removing some "stuck" agents, aborting them, such that other agents can continue. |
| 4 | wait2link | time, agent-id | After an agent departs, it must wait until it finds a space to enter the road. This is the moment the agent really enters the road. Often at the same time as 6-departure, but not always. |
| 5 | entered link | time, agent-id, link-id | Issued if an agent crosses a node (see 2-left link) |
| 6 | departure | time, agent-id, link-id | when an agent departs at a location |
| 7 | actstart | time, agent-id, link-id, act-type | when an agent starts performing an activity |
| 8 | actend | time, agent-id, link-id, act-type | when an agent ends performing an activity |
| 9 | agentMoney | time, agent-id, amount | an agent earns some amount of money (e.g. -5 if it has to pay a toll) |
The following example shows the events of one agent, starting at home and driving to work:
T_GBL VEH_ID LEG_NR LINK_ID FROM_NODE_ID EVENT_FLAG DESCRIPTION21610 1 0 1 0 8 actend home21610 1 0 1 0 6 departure21612 1 0 1 0 4 wait2link21640 1 0 1 0 2 left link21640 1 0 2 0 5 entered link21740 1 0 2 0 2 left link21740 1 0 3 0 5 entered link21820 1 0 3 0 2 left link21820 1 0 4 0 5 entered link21890 1 0 4 0 0 arrival21890 1 0 4 0 7 actstart work
| eventsOverview.png 50.91 KB |