Demand events configuration

The configuration of the demand events proceed through two couples of parameters, associated to TRE offline and online behavior:

Offline parameters
- SaveDemandEvent
- DemandEventBinaryDataPeriodization
Online parameters
- UseDemandEvents
- ReRoutingPeriodization

Parameter	Offline/Online
SaveDemandEvent	Offline. Data type: Boolean Associated to the binary data of the demand events. true: Export the binary data for the demand events at the end of the simulation. false: Don't export the binary data. See also → Equilibrium parameters.
DemandEventBinaryDataPeriodization	Offline. Data type: Integer Represents the interval length (in seconds) for the demand event binary data. The smaller the interval, the larger the file size. DemandEventBinaryDataPeriodization< ResIntD are not useful (→ ResIntD). DemandEventBinaryDataPeriodization=-1 means use the same value of ResIntD. See also → Equilibrium parameters.
UseDemandEvents	Online. Data type: Boolean Handles demand events. true: Demand events are handled. false: Otherwise. See also → Rerouting parameters.
ReRoutingPeriodization	Online. Data type: Integer. Defines the time interval, measured in seconds [s], for the turn probabilities evaluation for rerouting and demand events. The node model splitting rates are computed periodically every ReRoutingPeriodization interval, accordingly to the event data. The value assigned to ReRoutingPeriodization influences two contrasting characteristics: The quality of the results. The computational cost. The smaller the value, the higher is the accuracy of the results, but the computational cost is also increased, possibly to the point where the run time overcomes the maximum allowed time. It is the modeler's responsibility to evaluate these properties, according with the specific traffic network and all the associated characteristics. Important: You must set a value of ReRoutingPeriodization that maintains the run time acceptable with the highest quality. A consistent margin must be considered in the computation time as it can fluctuate between different computation. Important: The value used here can never be higher than the value set for DtaIntD. See also → Rerouting parameters.