Defining simulation parameters

ID of simulation run. Is added at the beginning of output file. To save the comment to the network file *.inpx, on the File menu, click > Save.

Simulation time in simulation seconds. You also need to account for lead times of signal controls.

The simulation start time is at simulation second 0 (Information in the status bar).

For signal control procedures with a date-dependent logic, the start date is transferred to the controller DLL. Format: DD.MM.YYYY

Number of time steps per simulation second: specifies how often vehicles and pedestrian are move in a simulation second.

• The position of vehicles is recalculated in a simulation second with each time step. The simulation resolution specifies the number of time steps.
• The position of pedestrians is calculated 20 times per simulation second. This is also the case when the simulation resolution specifies less time steps. The simulation resolution then defines the following functions for pedestrians:
• how often pedestrian movement is updated per simulation second
• how often pedestrians can be reintroduced into the simulation per simulation second
• how often pedestrians can make routing decisions per simulation second
• how often evaluations may be performed per simulation second

Value range: integers from 1 to 20

• Values < 5 lead to jerky movements. This is why this value range is less suitable for production of the final simulation results. As lower values accelerate the simulation, the use of lower values during setup of the network model can be helpful.
• Values between 5 and 10 lead to a more realistic demonstration. This value range is suitable for the production of the final simulation results.
• Values between 10 and 20 lead to smoother movements. This value range is suitable for high-quality simulation animations.

This value initializes a random number generator. Two simulation runs using the same network file and random start number look the same. If you vary the random seed, the stochastic functions in Vissim are assigned a different value sequence and the traffic flow changes. This, e.g., allows you to simulate stochastic variations of vehicle arrivals in the network. This can lead to different simulation results. A comparison of these simulation results allows you to compare the effect of stochastic variations. For this purpose, Vissim calculates additional, meaningful values for various result attributes during its evaluations, e.g. minimum value, maximum value and mean.

Number of runs of multiple simulation that were performed in a row. Logical value range: depends on use case 5 - 20.

For dynamic assignment, more than 20 simulation runs may be necessary.

Difference between random seeds when you perform multiple simulation runs. This number is irrelevant for stochastic distribution.

For the model to converge during dynamic assignment, enter 0.

When you perform multiple simulation runs using different random seeds, the number of the respective simulation run is added to the name of the evaluation file *.ldp.

For dynamic assignment only: Increases total demand of the origin-destination matrix with each simulation run defined (in the Number of runs box) by the value specified.

The start value used is the parameter Scale total volume to of dynamic assignment (Attributes for the trip chain file, matrices, path file and cost file). For each iteration, the demand is automatically increased by this value until 100% of the total demand is reached. Once 100 % of the total demand is reached, any additional simulation runs (as specified in the Number of runs box) will be performed using 100 % of the total demand. Avoid using a start value larger than 100% of the total demand.

If due to the Number of runs specified you do not perform enough simulation runs to reach 100 % of the total demand and you then save the Vissim network, the current value of the total demand is saved to the parameter Scale total volume to of dynamic assignment. The next time you open Vissim, this value will be used as the new start value.

Corresponds to a time lapse factor: Indicates simulation seconds per real-time second

Value 1.0: The simulation is run in real-time.

Value 2.0: The simulation is run at double real-time speed.

Maximum option: Select this option to run the simulation at the maximum speed.

The simulation speed does not affect the simulation results. You can change the simulation speed during the simulation run.

The desired simulation speed might not be reached, if you are using a large networks or a slower computer.

 Select this option if at the end of a time interval, you do not want Vissim to wait until the real-time set for this interval has elapsed.

Instead, Vissim will wait until the real-time for all time intervals, since continuous simulation was last started, has elapsed. This allows VISSIM to make up for the time lost through slower, individual time intervals, e.g. due to external signal control or other external factors. With the help of external controller hardware, the synchronization function ensures that the time lost is regained.

If you open a window during a continuous simulation run in Vissim, this can cause a delay. After you close the window, the delay is made up for through maximum simulation speed, until the simulation second divided by the simulation speed equals the total real-time elapsed.

When the simulation speed of a continuous simulation run is reduced through retrospective synchronization, Vissim waits until the total real-time (since simulation start) equals the current simulation second divided by the simulation speed, before it executes the next time interval.

Number of processor cores used during simulation. The maximum number of cores used depends on your computer. Your setting remains selected when you start the next simulation run.

Default: Use all cores

The number of cores selected is saved to the network file *.inpx. You cannot change this setting during the simulation run.