Difference between revisions of "SUMO"

From Sumo
Jump to navigation Jump to search
m (minor rewording)
 
(30 intermediate revisions by 3 users not shown)
Line 12: Line 12:
  
 
=Usage Description=
 
=Usage Description=
 +
For a brief overview see [[Simulation/Basic_Definition]]. Model details and feature documentation can be found at [[SUMO_User_Documentation#Simulation|Simulation topics]].
 +
 
==Options==
 
==Options==
You may use a XML schema definition file for setting up a SUMO configuration: [http://sumo-sim.org/xsd/sumoConfiguration.xsd sumoConfiguration.xsd].
+
You may use a XML schema definition file for setting up a SUMO configuration: [http://sumo.dlr.de/xsd/sumoConfiguration.xsd sumoConfiguration.xsd].
 
===Configuration===
 
===Configuration===
 
{| class="wikitable" style="width:90%"
 
{| class="wikitable" style="width:90%"
Line 23: Line 25:
 
| style="vertical-align:top" | Loads the named config on startup
 
| style="vertical-align:top" | Loads the named config on startup
 
|-
 
|-
| style="vertical-align:top" | {{Option|--save-configuration {{DT_FILE}}}}
+
| style="vertical-align:top" | {{Option|-C {{DT_FILE}}}}<br/> {{Option|--save-configuration {{DT_FILE}}}}
 
| style="vertical-align:top" | Saves current configuration into FILE
 
| style="vertical-align:top" | Saves current configuration into FILE
 
|-
 
|-
Line 62: Line 64:
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--load-state.offset {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--load-state.offset {{DT_TIME}}}}
| style="vertical-align:top" | Sets the time offset for vehicle segment exit times; ''default: '''0'''''
+
| style="vertical-align:top" | Shifts all times loaded from a saved state by the given offset; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--load-state.remove-vehicles {{DT_STR}}}}
 +
| style="vertical-align:top" | Removes vehicles with the given IDs from the loaded state
 
|-
 
|-
 
|}
 
|}
Line 71: Line 76:
 
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 
! style="background:#ddffdd; vertical-align:top" | Description
 
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--write-license {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Include license info into every output file; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--output-prefix {{DT_STR}}}}
 +
| style="vertical-align:top" | Prefix which is applied to all output files. The special string 'TIME' is replaced by the current time.
 +
|-
 +
| style="vertical-align:top" | {{Option|--precision {{DT_INT}}}}
 +
| style="vertical-align:top" | Defines the number of digits after the comma for floating point output; ''default: '''2'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--precision.geo {{DT_INT}}}}
 +
| style="vertical-align:top" | Defines the number of digits after the comma for lon,lat output; ''default: '''6'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|-H {{DT_BOOL}}}}<br/> {{Option|--human-readable-time {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Write time values as hour:minute:second or day:hour:minute:second rathern than seconds; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--netstate-dump {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--netstate-dump {{DT_FILE}}}}
Line 77: Line 97:
 
| style="vertical-align:top" | {{Option|--netstate-dump.empty-edges {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--netstate-dump.empty-edges {{DT_BOOL}}}}
 
| style="vertical-align:top" | Write also empty edges completely when dumping; ''default: '''false'''''
 
| style="vertical-align:top" | Write also empty edges completely when dumping; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--netstate-dump.precision {{DT_INT}}}}
 +
| style="vertical-align:top" | Write positions and speeds with the given precision (default 2); ''default: '''2'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--emission-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--emission-output {{DT_FILE}}}}
 
| style="vertical-align:top" | Save the emission values of each vehicle
 
| style="vertical-align:top" | Save the emission values of each vehicle
 +
|-
 +
| style="vertical-align:top" | {{Option|--emission-output.precision {{DT_INT}}}}
 +
| style="vertical-align:top" | Write emission values with the given precision (default 2); ''default: '''2'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--battery-output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Save the battery values of each vehicle
 +
|-
 +
| style="vertical-align:top" | {{Option|--battery-output.precision {{DT_INT}}}}
 +
| style="vertical-align:top" | Write battery values with the given precision (default 2); ''default: '''2'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--chargingstations-output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Write data of charging stations
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--fcd-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--fcd-output {{DT_FILE}}}}
Line 89: Line 124:
 
| style="vertical-align:top" | {{Option|--fcd-output.signals {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--fcd-output.signals {{DT_BOOL}}}}
 
| style="vertical-align:top" | Add the vehicle signal state to the FCD output (brake lights etc.); ''default: '''false'''''
 
| style="vertical-align:top" | Add the vehicle signal state to the FCD output (brake lights etc.); ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--fcd-output.distance {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Add kilometrage to the FCD output (linear referencing); ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--fcd-output.filter-edges.input-file {{DT_FILE}}}}
 +
| style="vertical-align:top" | Restrict fcd output to the edge selection from the given input file
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--full-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--full-output {{DT_FILE}}}}
Line 98: Line 139:
 
| style="vertical-align:top" | {{Option|--vtk-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--vtk-output {{DT_FILE}}}}
 
| style="vertical-align:top" | Save complete vehicle positions inclusive speed values in the VTK Format (usage: /path/out will produce /path/out_$TIMESTEP$.vtp files)
 
| style="vertical-align:top" | Save complete vehicle positions inclusive speed values in the VTK Format (usage: /path/out will produce /path/out_$TIMESTEP$.vtp files)
 +
|-
 +
| style="vertical-align:top" | {{Option|--amitran-output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Save the vehicle trajectories in the Amitran format
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--summary-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--summary-output {{DT_FILE}}}}
Line 104: Line 148:
 
| style="vertical-align:top" | {{Option|--tripinfo-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--tripinfo-output {{DT_FILE}}}}
 
| style="vertical-align:top" | Save single vehicle trip info into FILE
 
| style="vertical-align:top" | Save single vehicle trip info into FILE
 +
|-
 +
| style="vertical-align:top" | {{Option|--tripinfo-output.write-unfinished {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Write tripinfo output for vehicles which have not arrived at simulation end; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--vehroute-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--vehroute-output {{DT_FILE}}}}
Line 116: Line 163:
 
| style="vertical-align:top" | {{Option|--vehroute-output.sorted {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--vehroute-output.sorted {{DT_BOOL}}}}
 
| style="vertical-align:top" | Sorts the output by departure time; ''default: '''false'''''
 
| style="vertical-align:top" | Sorts the output by departure time; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--vehroute-output.dua {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Write the output in the duarouter alternatives style; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--vehroute-output.cost {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Write costs for all routes; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--vehroute-output.intended-depart {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Write the output with the intended instead of the real departure time; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--vehroute-output.route-length {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Include total route length in the output; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--vehroute-output.write-unfinished {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--vehroute-output.write-unfinished {{DT_BOOL}}}}
 
| style="vertical-align:top" | Write vehroute output for vehicles which have not arrived at simulation end; ''default: '''false'''''
 
| style="vertical-align:top" | Write vehroute output for vehicles which have not arrived at simulation end; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--vehroute-output.skip-ptlines {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Skip vehroute output for public transport vehicles; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--vehroute-output.incomplete {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Include invalid routes and route stubs in vehroute output; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--link-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--link-output {{DT_FILE}}}}
 
| style="vertical-align:top" | Save links states into FILE
 
| style="vertical-align:top" | Save links states into FILE
 +
|-
 +
| style="vertical-align:top" | {{Option|--railsignal-block-output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Save railsignal-blocks into FILE
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--bt-output {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--bt-output {{DT_FILE}}}}
| style="vertical-align:top" | Save bt visibilities into FILE
+
| style="vertical-align:top" | Save bluetooth visibilities into FILE (in conjunction with device.btreceiver and device.btsender)
 +
|-
 +
| style="vertical-align:top" | {{Option|--lanechange-output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Record lane changes and their motivations for all vehicles into FILE
 +
|-
 +
| style="vertical-align:top" | {{Option|--lanechange-output.started {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Record start of lane change manoeuvres; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--lanechange-output.ended {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Record end of lane change manoeuvres; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--stop-output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Record stops and loading/unloading of passenger and containers for all vehicles into FILE
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--save-state.times {{DT_INT[]}}}}
 
| style="vertical-align:top" | {{Option|--save-state.times {{DT_INT[]}}}}
 
| style="vertical-align:top" | Use INT[] as times at which a network state written
 
| style="vertical-align:top" | Use INT[] as times at which a network state written
 +
|-
 +
| style="vertical-align:top" | {{Option|--save-state.period {{DT_TIME}}}}
 +
| style="vertical-align:top" | save state repeatedly after TIME period; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--save-state.prefix {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--save-state.prefix {{DT_FILE}}}}
 
| style="vertical-align:top" | Prefix for network states; ''default: '''state'''''
 
| style="vertical-align:top" | Prefix for network states; ''default: '''state'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--save-state.suffix {{DT_STR}}}}
 +
| style="vertical-align:top" | Suffix for network states (.sbx or .xml); ''default: '''.sbx'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--save-state.files {{DT_FILE}}}}
 
| style="vertical-align:top" | {{Option|--save-state.files {{DT_FILE}}}}
Line 144: Line 230:
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-b {{DT_TIME}}}}<br/> {{Option|--begin {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|-b {{DT_TIME}}}}<br/> {{Option|--begin {{DT_TIME}}}}
| style="vertical-align:top" | Defines the begin time; The simulation starts at this time; ''default: '''0'''''
+
| style="vertical-align:top" | Defines the begin time in seconds; The simulation starts at this time; ''default: '''0'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-e {{DT_TIME}}}}<br/> {{Option|--end {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|-e {{DT_TIME}}}}<br/> {{Option|--end {{DT_TIME}}}}
| style="vertical-align:top" | Defines the end time; The simulation ends at this time; ''default: '''-1'''''
+
| style="vertical-align:top" | Defines the end time in seconds; The simulation ends at this time; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--step-length {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--step-length {{DT_TIME}}}}
| style="vertical-align:top" | Defines the step duration; ''default: '''1'''''
+
| style="vertical-align:top" | Defines the step duration in seconds; ''default: '''1'''''
 
|-
 
|-
 
|}
 
|}
Line 159: Line 245:
 
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 
! style="background:#ddffdd; vertical-align:top" | Description
 
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--step-method.ballistic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Whether to use ballistic method for the positional update of vehicles (default is a semi-implicit Euler method).; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--threads {{DT_INT}}}}
 +
| style="vertical-align:top" | Defines the number of threads for parallel simulation; ''default: '''1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--lateral-resolution {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Defines the resolution in m when handling lateral positioning within a lane (with -1 all vehicles drive at the center of their lane; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-s {{DT_TIME}}}}<br/> {{Option|--route-steps {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|-s {{DT_TIME}}}}<br/> {{Option|--route-steps {{DT_TIME}}}}
Line 168: Line 263:
 
| style="vertical-align:top" | {{Option|--ignore-junction-blocker {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--ignore-junction-blocker {{DT_TIME}}}}
 
| style="vertical-align:top" | Ignore vehicles which block the junction after they have been standing for SECONDS (-1 means never ignore); ''default: '''-1'''''
 
| style="vertical-align:top" | Ignore vehicles which block the junction after they have been standing for SECONDS (-1 means never ignore); ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--ignore-route-errors {{DT_BOOL}}}}
 +
| style="vertical-align:top" | (1) Do not check whether routes are connected. (2) Allow inserting a vehicle in a situation which requires emergency braking.; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--ignore-accidents {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--ignore-accidents {{DT_BOOL}}}}
| style="vertical-align:top" | Do not check whether accidents occure more deeply; ''default: '''false'''''
+
| style="vertical-align:top" | Do not check whether accidents occur; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--collision.action {{DT_STR}}}}
 +
| style="vertical-align:top" | How to deal with collisions: [none,warn,teleport,remove]; ''default: '''teleport'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--collision.stoptime {{DT_TIME}}}}
 +
| style="vertical-align:top" | Let vehicle stop for TIME before performing collision.action (except for action 'none'); ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--collision.check-junctions {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enables collisions checks on junctions; ''default: '''false'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--ignore-route-errors {{DT_BOOL}}}}
+
| style="vertical-align:top" | {{Option|--collision.mingap-factor {{DT_FLOAT}}}}
| style="vertical-align:top" | Do not check whether routes are connected; ''default: '''false'''''
+
| style="vertical-align:top" | Sets the fraction of minGap that must be maintained to avoid collision detection. If a negative value is given, the carFollowModel parameter is used; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--max-num-vehicles {{DT_INT}}}}
 
| style="vertical-align:top" | {{Option|--max-num-vehicles {{DT_INT}}}}
| style="vertical-align:top" | Quit simulation if this number of vehicles is exceeded; ''default: '''-1'''''
+
| style="vertical-align:top" | Delay vehicle insertion to stay within the given maximum number; ''default: '''-1'''''
|-
 
| style="vertical-align:top" | {{Option|--incremental-dua-step {{DT_INT}}}}
 
| style="vertical-align:top" | Perform the simulation as a step in incremental DUA
 
 
|-
 
|-
| style="vertical-align:top" | {{Option|--incremental-dua-base {{DT_INT}}}}
+
| style="vertical-align:top" | {{Option|--max-num-teleports {{DT_INT}}}}
| style="vertical-align:top" | Base value for incremental DUA; ''default: '''10'''''
+
| style="vertical-align:top" | Abort the simulation if the given maximum number of teleports is exceeded; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--scale {{DT_FLOAT}}}}
 
| style="vertical-align:top" | {{Option|--scale {{DT_FLOAT}}}}
| style="vertical-align:top" | Scale demand by the given factor (0..1)
+
| style="vertical-align:top" | Scale demand by the given factor (by discarding or duplicating vehicles); ''default: '''1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--time-to-teleport {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--time-to-teleport {{DT_TIME}}}}
Line 191: Line 295:
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--time-to-teleport.highways {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--time-to-teleport.highways {{DT_TIME}}}}
| style="vertical-align:top" | The teleport time on highways; ''default: '''0'''''
+
| style="vertical-align:top" | The waiting time after which vehicles on a fast road (speed > 69m/s) are teleported if they are on a non-continuing lane; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--waiting-time-memory {{DT_TIME}}}}
 +
| style="vertical-align:top" | Length of time interval, over which accumulated waiting time is taken into account (default is 100s.); ''default: '''100'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--max-depart-delay {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--max-depart-delay {{DT_TIME}}}}
Line 204: Line 311:
 
| style="vertical-align:top" | {{Option|--random-depart-offset {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--random-depart-offset {{DT_TIME}}}}
 
| style="vertical-align:top" | Each vehicle receives a random offset to its depart value drawn uniformly from [0, TIME]; ''default: '''0'''''
 
| style="vertical-align:top" | Each vehicle receives a random offset to its depart value drawn uniformly from [0, TIME]; ''default: '''0'''''
|-
 
| style="vertical-align:top" | {{Option|--lanechange.allow-swap {{DT_BOOL}}}}
 
| style="vertical-align:top" | Whether blocking vehicles trying to change lanes may be swapped; ''default: '''false'''''
 
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--lanechange.duration {{DT_TIME}}}}
 
| style="vertical-align:top" | {{Option|--lanechange.duration {{DT_TIME}}}}
Line 214: Line 318:
 
| style="vertical-align:top" | Whether overtaking on the right on motorways is permitted; ''default: '''false'''''
 
| style="vertical-align:top" | Whether overtaking on the right on motorways is permitted; ''default: '''false'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--routing-algorithm {{DT_STR}}}}
+
| style="vertical-align:top" | {{Option|--tls.all-off {{DT_BOOL}}}}
| style="vertical-align:top" | Select among routing algorithms ['dijkstra', 'astar']; ''default: '''dijkstra'''''
+
| style="vertical-align:top" | Switches off all traffic lights.; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--tls.actuated.show-detectors {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Sets default visibility for actuation detectors; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--tls.delay_based.detector-range {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Sets default range for detecting delayed vehicles; ''default: '''100'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--time-to-impatience {{DT_TIME}}}}
 +
| style="vertical-align:top" | Specify how long a vehicle may wait until impatience grows from 0 to 1, defaults to 300, non-positive values disable impatience growth; ''default: '''300'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--default.action-step-length {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Length of the default interval length between action points for the car-following and lane-change models (in seconds). If not specified, the simulation step-length is used per default. Vehicle- or VType-specific settings override the default. Must be a multiple of the simulation step-length.; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--default.carfollowmodel {{DT_STR}}}}
 +
| style="vertical-align:top" | Select default car following model (Krauss, IDM, ...); ''default: '''Krauss'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--default.speeddev {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Select default speed deviation. A negative value implies vClass specific defaults (0.1 for the default passenger class; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--default.emergencydecel {{DT_STR}}}}
 +
| style="vertical-align:top" | Select default emergencyDecel value among ('decel', 'default', FLOAT) which sets the value either to the same as the deceleration value, a vClass-class specific default or the given FLOAT in m/s^2; ''default: '''default'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--emergencydecel.warning-threshold {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Sets the fraction of emergency decel capability that must be used to trigger a warning.; ''default: '''1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--pedestrian.model {{DT_STR}}}}
 
| style="vertical-align:top" | {{Option|--pedestrian.model {{DT_STR}}}}
| style="vertical-align:top" | Select among pestrian models ['striping', 'nonInteracting']; ''default: '''striping'''''
+
| style="vertical-align:top" | Select among pedestrian models ['nonInteracting', 'striping', 'remote']; ''default: '''striping'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--pedestrian.striping.stripe-width {{DT_FLOAT}}}}
 
| style="vertical-align:top" | {{Option|--pedestrian.striping.stripe-width {{DT_FLOAT}}}}
| style="vertical-align:top" | Width of parallel stripes for segmenting a sidewalk (in meters) for use with model 'striping'; ''default: '''0.65'''''
+
| style="vertical-align:top" | Width of parallel stripes for segmenting a sidewalk (meters) for use with model 'striping'; ''default: '''0.64'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--pedestrian.striping.dawdling {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Factor for random slow-downs [0,1] for use with model 'striping'; ''default: '''0.2'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--pedestrian.striping.jamtime {{DT_TIME}}}}
 +
| style="vertical-align:top" | Time in seconds after which pedestrians start squeezing through a jam when using model 'striping' (non-positive values disable squeezing); ''default: '''300'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--pedestrian.striping.jamtime.crossing {{DT_TIME}}}}
 +
| style="vertical-align:top" | Time in seconds after which pedestrians start squeezing through a jam while on a pedestrian crossing when using model 'striping' (non-positive values disable squeezing); ''default: '''10'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--pedestrian.remote.address {{DT_STR}}}}
 +
| style="vertical-align:top" | The address (host:port) of the external simulation; ''default: '''localhost:9000'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--pedestrina.striping.dawdling {{DT_FLOAT}}}}
+
| style="vertical-align:top" | {{Option|--ride.stop-tolerance {{DT_FLOAT}}}}
| style="vertical-align:top" | Factor for random slow-downs [0,1] for use with model 'striping'; ''default: '''0.5'''''
+
| style="vertical-align:top" | Tolerance to apply when matching pedestrian and vehicle positions on boarding at individual stops; ''default: '''10'''''
 +
|-
 +
|}
 +
 
 +
===Routing===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--routing-algorithm {{DT_STR}}}}
 +
| style="vertical-align:top" | Select among routing algorithms ['dijkstra', 'astar', 'CH', 'CHWrapper']; ''default: '''dijkstra'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--weights.random-factor {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Edge weights for routing are dynamically disturbed by a random factor drawn uniformly from [1,FLOAT); ''default: '''1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--weights.minor-penalty {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Apply the given time penalty when computing minimum routing costs for minor-link internal lanes; ''default: '''1.5'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--astar.all-distances {{DT_FILE}}}}
 +
| style="vertical-align:top" | Initialize lookup table for astar from the given file (generated by marouter --all-pairs-output)
 +
|-
 +
| style="vertical-align:top" | {{Option|--astar.landmark-distances {{DT_FILE}}}}
 +
| style="vertical-align:top" | Initialize lookup table for astar ALT-variant from the given file
 +
|-
 +
| style="vertical-align:top" | {{Option|--persontrip.walkfactor {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Use FLOAT as a factor on pedestrian maximum speed during intermodal routing; ''default: '''0.75'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--persontrip.transfer.car-walk {{DT_STR}}}}
 +
| style="vertical-align:top" | Where are mode changes from car to walking allowed (possible values: 'parkingAreas', 'ptStops', 'allJunctions' and combinations); ''default: '''parkingAreas'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a vehicle to have a 'rerouting' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'rerouting' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'rerouting' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.period {{DT_TIME}}}}
 +
| style="vertical-align:top" | The period with which the vehicle shall be rerouted; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.pre-period {{DT_TIME}}}}
 +
| style="vertical-align:top" | The rerouting period before depart; ''default: '''60'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.adaptation-weight {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The weight of prior edge weights for exponential moving average; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.adaptation-steps {{DT_INT}}}}
 +
| style="vertical-align:top" | The number of steps for moving average weight of prior edge weights; ''default: '''180'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.adaptation-interval {{DT_TIME}}}}
 +
| style="vertical-align:top" | The interval for updating the edge weights; ''default: '''1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.with-taz {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Use zones (districts) as routing start- and endpoints; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.init-with-loaded-weights {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Use weight files given with option --weight-files for initializing edge weights; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.threads {{DT_INT}}}}
 +
| style="vertical-align:top" | The number of parallel execution threads used for rerouting; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.synchronize {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Let rerouting happen at the same time for all vehicles; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.rerouting.output {{DT_FILE}}}}
 +
| style="vertical-align:top" | Save adapting weights to FILE
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.rerouting.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a person to have a 'rerouting' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.rerouting.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'rerouting' device to named persons
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.rerouting.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'rerouting' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.rerouting.period {{DT_TIME}}}}
 +
| style="vertical-align:top" | The period with which the person shall be rerouted; ''default: '''0'''''
 
|-
 
|-
 
|}
 
|}
Line 237: Line 457:
 
| style="vertical-align:top" | Switches to verbose output; ''default: '''false'''''
 
| style="vertical-align:top" | Switches to verbose output; ''default: '''false'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|-p {{DT_BOOL}}}}<br/> {{Option|--print-options {{DT_BOOL}}}}
+
| style="vertical-align:top" | {{Option|--print-options {{DT_BOOL}}}}
 
| style="vertical-align:top" | Prints option values before processing; ''default: '''false'''''
 
| style="vertical-align:top" | Prints option values before processing; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-? {{DT_BOOL}}}}<br/> {{Option|--help {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|-? {{DT_BOOL}}}}<br/> {{Option|--help {{DT_BOOL}}}}
| style="vertical-align:top" | Prints this screen; ''default: '''false'''''
+
| style="vertical-align:top" | Prints this screen or selected topics; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-V {{DT_BOOL}}}}<br/> {{Option|--version {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|-V {{DT_BOOL}}}}<br/> {{Option|--version {{DT_BOOL}}}}
Line 264: Line 484:
 
| style="vertical-align:top" | Writes all warnings and errors to FILE
 
| style="vertical-align:top" | Writes all warnings and errors to FILE
 
|-
 
|-
| style="vertical-align:top" | {{Option|--no-duration-log {{DT_BOOL}}}}
+
| style="vertical-align:top" | {{Option|--duration-log.disable {{DT_BOOL}}}}
 
| style="vertical-align:top" | Disable performance reports for individual simulation steps; ''default: '''false'''''
 
| style="vertical-align:top" | Disable performance reports for individual simulation steps; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--duration-log.statistics {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable statistics on vehicle trips; ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--no-step-log {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--no-step-log {{DT_BOOL}}}}
Line 282: Line 505:
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.emissions.probability {{DT_FLOAT}}}}
 
| style="vertical-align:top" | {{Option|--device.emissions.probability {{DT_FLOAT}}}}
| style="vertical-align:top" | The probability for a vehicle to have an emission logging device; ''default: '''0'''''
+
| style="vertical-align:top" | The probability for a vehicle to have a 'emissions' device; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.emissions.explicit {{DT_STR}}}}
 
| style="vertical-align:top" | {{Option|--device.emissions.explicit {{DT_STR}}}}
| style="vertical-align:top" | Assign a device to named vehicles
+
| style="vertical-align:top" | Assign a 'emissions' device to named vehicles
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.emissions.deterministic {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--device.emissions.deterministic {{DT_BOOL}}}}
| style="vertical-align:top" | The devices are set deterministic using a fraction of 1000; ''default: '''false'''''
+
| style="vertical-align:top" | The 'emissions' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 
|-
 
|-
 
|}
 
|}
Line 299: Line 522:
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.btreceiver.probability {{DT_FLOAT}}}}
 
| style="vertical-align:top" | {{Option|--device.btreceiver.probability {{DT_FLOAT}}}}
| style="vertical-align:top" | The probability for a vehicle to have a 'btreceiver' device; ''default: '''0'''''
+
| style="vertical-align:top" | The probability for a vehicle to have a 'btreceiver' device; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.btreceiver.explicit {{DT_STR}}}}
 
| style="vertical-align:top" | {{Option|--device.btreceiver.explicit {{DT_STR}}}}
Line 312: Line 535:
 
| style="vertical-align:top" | {{Option|--device.btreceiver.all-recognitions {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|--device.btreceiver.all-recognitions {{DT_BOOL}}}}
 
| style="vertical-align:top" | Whether all recognition point shall be written; ''default: '''false'''''
 
| style="vertical-align:top" | Whether all recognition point shall be written; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.btreceiver.offtime {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The offtime used for calculating detection probability (in seconds); ''default: '''0.64'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.btsender.probability {{DT_FLOAT}}}}
 
| style="vertical-align:top" | {{Option|--device.btsender.probability {{DT_FLOAT}}}}
| style="vertical-align:top" | The probability for a vehicle to have a 'btsender' device; ''default: '''0'''''
+
| style="vertical-align:top" | The probability for a vehicle to have a 'btsender' device; ''default: '''-1'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|--device.btsender.explicit {{DT_STR}}}}
 
| style="vertical-align:top" | {{Option|--device.btsender.explicit {{DT_STR}}}}
Line 324: Line 550:
 
|}
 
|}
  
===Routing===
+
===Battery===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.battery.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a vehicle to have a 'battery' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.battery.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'battery' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.battery.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'battery' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
|}
 +
 
 +
===Example Device===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.example.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a vehicle to have a 'example' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.example.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'example' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.example.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'example' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.example.parameter {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | An exemplary parameter which can be used by all instances of the example device; ''default: '''0'''''
 +
|-
 +
|}
 +
 
 +
===Ssm Device===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a vehicle to have a 'ssm' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'ssm' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'ssm' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.measures {{DT_STR}}}}
 +
| style="vertical-align:top" | Specifies which measures will be logged (as a space separated sequence of IDs in ('TTC', 'DRAC', 'PET')).
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.thresholds {{DT_STR}}}}
 +
| style="vertical-align:top" | Specifies thresholds corresponding to the specified measures (see documentation and watch the order!). Only events exceeding the thresholds will be logged.
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.trajectories {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Specifies whether trajectories will be logged (if false, only the extremal values and times are reported, this is the default).
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.range {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Specifies the detection range in meters (default is 50.00m.). For vehicles below this distance from the equipped vehicle, SSM values are traced.
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.extratime {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Specifies the time in seconds to be logged after a conflict is over (default is 5.00secs.). Required >0 if PET is to be calculated for crossing conflicts.
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.file {{DT_STR}}}}
 +
| style="vertical-align:top" | Give a global default filename for the SSM output.
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.ssm.geo {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Whether to use coordinates of the original reference system in output (default is false).
 +
|-
 +
|}
 +
 
 +
===Toc Device===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a vehicle to have a 'toc' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'toc' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'toc' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.manualType {{DT_STR}}}}
 +
| style="vertical-align:top" | Vehicle type for manual driving regime.
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.automatedType {{DT_STR}}}}
 +
| style="vertical-align:top" | Vehicle type for automated driving regime.
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.responseTime {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Average response time needed by a driver to take back control.; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.recoveryRate {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Recovery rate for the driver's awareness after a ToC.; ''default: '''0.1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.lcAbstinence {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Attention level below which a driver restrains from performing lane changes (value in [0,1]).; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.initialAwareness {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Average awareness a driver has initially after a ToC (value in [0,1]).; ''default: '''0.5'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.mrmDecel {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Deceleration rate applied during a 'minimum risk maneuver'.; ''default: '''1.5'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.dynamicToCThreshold {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Time, which the vehicle requires to have ahead to continue in automated mode. The default value of 0 indicates no dynamic triggering of ToCs.; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.dynamicMRMProbability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Probability that a dynamically triggered TOR is not answered in time.; ''default: '''0.05'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.mrmKeepRight {{DT_BOOL}}}}
 +
| style="vertical-align:top" | If true, the vehicle tries to change to the right during an MRM.; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.maxPreparationAccel {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Maximal acceleration that may be applied during the ToC preparation phase.; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.ogNewTimeHeadway {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Timegap for ToC preparation phase.; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.ogNewSpaceHeadway {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Additional spacing for ToC preparation phase.; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.ogMaxDecel {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Maximal deceleration applied for establishing increased gap in ToC preparation phase.; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.ogChangeRate {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Rate of adaptation towards the increased headway during ToC preparation.; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.useColorScheme {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Whether a coloring scheme shall by applied to indicate the different ToC stages.; ''default: '''true'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.toc.file {{DT_STR}}}}
 +
| style="vertical-align:top" | Switches on output by specifying an output filename.
 +
|-
 +
|}
 +
 
 +
===Driver State Device===
 
{| class="wikitable" style="width:90%"
 
{| class="wikitable" style="width:90%"
 
|-
 
|-
Line 330: Line 699:
 
! style="background:#ddffdd; vertical-align:top" | Description
 
! style="background:#ddffdd; vertical-align:top" | Description
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.probability {{DT_FLOAT}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.probability {{DT_FLOAT}}}}
| style="vertical-align:top" | The probability for a vehicle to have a 'rerouting' device; ''default: '''0'''''
+
| style="vertical-align:top" | The probability for a vehicle to have a 'driverstate' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.driverstate.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'driverstate' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.driverstate.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'driverstate' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.driverstate.initialAwareness {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Initial value assigned to the driver's awareness.; ''default: '''1'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.explicit {{DT_STR}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.errorTimeScaleCoefficient {{DT_FLOAT}}}}
| style="vertical-align:top" | Assign a 'rerouting' device to named vehicles
+
| style="vertical-align:top" | Time scale for the error process.; ''default: '''100'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.deterministic {{DT_BOOL}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.errorNoiseIntensityCoefficient {{DT_FLOAT}}}}
| style="vertical-align:top" | The 'rerouting' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
+
| style="vertical-align:top" | Noise intensity driving the error process.; ''default: '''0.2'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.period {{DT_TIME}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.speedDifferenceErrorCoefficient {{DT_FLOAT}}}}
| style="vertical-align:top" | The period with which the vehicle shall be rerouted; ''default: '''0'''''
+
| style="vertical-align:top" | General scaling coefficient for applying the error to the perceived speed difference (error also scales with distance).; ''default: '''0.15'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.pre-period {{DT_TIME}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.headwayErrorCoefficient {{DT_FLOAT}}}}
| style="vertical-align:top" | The rerouting period before depart; ''default: '''0'''''
+
| style="vertical-align:top" | General scaling coefficient for applying the error to the perceived distance (error also scales with distance).; ''default: '''0.75'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.adaptation-weight {{DT_FLOAT}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.speedDifferenceChangePerceptionThreshold {{DT_FLOAT}}}}
| style="vertical-align:top" | The weight of prior edge weights; ''default: '''0.5'''''
+
| style="vertical-align:top" | Base threshold for recognizing changes in the speed difference (threshold also scales with distance).; ''default: '''0.1'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.adaptation-interval {{DT_TIME}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.headwayChangePerceptionThreshold {{DT_FLOAT}}}}
| style="vertical-align:top" | The interval for updating the edge weights; ''default: '''1'''''
+
| style="vertical-align:top" | Base threshold for recognizing changes in the headway (threshold also scales with distance).; ''default: '''0.1'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.with-taz {{DT_BOOL}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.minAwareness {{DT_FLOAT}}}}
| style="vertical-align:top" | Use zones (districts) as routing end points; ''default: '''false'''''
+
| style="vertical-align:top" | Minimal admissible value for the driver's awareness.; ''default: '''0.1'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.rerouting.init-with-loaded-weights {{DT_BOOL}}}}
+
| style="vertical-align:top" | {{Option|--device.driverstate.maximalReactionTime {{DT_FLOAT}}}}
| style="vertical-align:top" | Use given weight files for initializing edge weights; ''default: '''false'''''
+
| style="vertical-align:top" | Maximal reaction time (~action step length) induced by decreased awareness level (reached for awareness=minAwareness).; ''default: '''-1'''''
 
|-
 
|-
 
|}
 
|}
  
===Example Device===
+
===Bluelight Device===
 
{| class="wikitable" style="width:90%"
 
{| class="wikitable" style="width:90%"
 
|-
 
|-
Line 365: Line 743:
 
! style="background:#ddffdd; vertical-align:top" | Description
 
! style="background:#ddffdd; vertical-align:top" | Description
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.example.explicit {{DT_STR}}}}
+
| style="vertical-align:top" | {{Option|--device.bluelight.probability {{DT_FLOAT}}}}
| style="vertical-align:top" | Assign a device to named vehicles
+
| style="vertical-align:top" | The probability for a vehicle to have a 'bluelight' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.bluelight.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'bluelight' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.bluelight.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'bluelight' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 
|-
 
|-
| style="vertical-align:top" | {{Option|--device.example.parameter {{DT_FLOAT}}}}
+
| style="vertical-align:top" | {{Option|--device.bluelight.parameter {{DT_FLOAT}}}}
 
| style="vertical-align:top" | An exemplary parameter which can be used by all instances of the example device; ''default: '''0'''''
 
| style="vertical-align:top" | An exemplary parameter which can be used by all instances of the example device; ''default: '''0'''''
 +
|-
 +
|}
 +
 +
===Fcd Device===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.fcd.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a vehicle to have a 'fcd' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.fcd.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'fcd' device to named vehicles
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.fcd.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'fcd' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--device.fcd.period {{DT_STR}}}}
 +
| style="vertical-align:top" | Recording period for FCD-data; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.fcd.probability {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The probability for a person to have a 'fcd' device; ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.fcd.explicit {{DT_STR}}}}
 +
| style="vertical-align:top" | Assign a 'fcd' device to named persons
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.fcd.deterministic {{DT_BOOL}}}}
 +
| style="vertical-align:top" | The 'fcd' devices are set deterministic using a fraction of 1000; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--person-device.fcd.period {{DT_STR}}}}
 +
| style="vertical-align:top" | Recording period for FCD-data; ''default: '''0'''''
 
|-
 
|-
 
|}
 
|}
Line 381: Line 797:
 
| style="vertical-align:top" | {{Option|--remote-port {{DT_INT}}}}
 
| style="vertical-align:top" | {{Option|--remote-port {{DT_INT}}}}
 
| style="vertical-align:top" | Enables TraCI Server if set; ''default: '''0'''''
 
| style="vertical-align:top" | Enables TraCI Server if set; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--num-clients {{DT_INT}}}}
 +
| style="vertical-align:top" | Expected number of connecting clients; ''default: '''1'''''
 +
|-
 +
|}
 +
 +
===Mesoscopic===
 +
{| class="wikitable" style="width:90%"
 +
|-
 +
! style="background:#ddffdd; vertical-align:top; width:350px" | Option
 +
! style="background:#ddffdd; vertical-align:top" | Description
 +
|-
 +
| style="vertical-align:top" | {{Option|--mesosim {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enables mesoscopic simulation; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-edgelength {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Length of an edge segment in mesoscopic simulation; ''default: '''98'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-tauff {{DT_TIME}}}}
 +
| style="vertical-align:top" | Factor for calculating the net free-free headway time; ''default: '''1.13'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-taufj {{DT_TIME}}}}
 +
| style="vertical-align:top" | Factor for calculating the net free-jam headway time; ''default: '''1.13'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-taujf {{DT_TIME}}}}
 +
| style="vertical-align:top" | Factor for calculating the jam-free headway time; ''default: '''1.73'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-taujj {{DT_TIME}}}}
 +
| style="vertical-align:top" | Factor for calculating the jam-jam headway time; ''default: '''1.4'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-jam-threshold {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Minimum percentage of occupied space to consider a segment jammed. A negative argument causes thresholds to be computed based on edge speed and tauff (default); ''default: '''-1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-multi-queue {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable multiple queues at edge ends; ''default: '''true'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-junction-control {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable mesoscopic traffic light and priority junction handling; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-junction-control.limited {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable mesoscopic traffic light and priority junction handling for saturated links. This prevents faulty traffic lights from hindering flow in low-traffic situations; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-tls-penalty {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | Apply scaled time penalties when driving across tls controlled junctions based on green split instead of checking actual phases; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-minor-penalty {{DT_TIME}}}}
 +
| style="vertical-align:top" | Apply fixed time penalty when driving across a minor link. When using --meso-junction-control.limited, the penalty is not applied whenever limited control is active.; ''default: '''0'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-overtaking {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable mesoscopic overtaking; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--meso-recheck {{DT_TIME}}}}
 +
| style="vertical-align:top" | Time interval for rechecking insertion into the next segment after failure; ''default: '''0'''''
 
|-
 
|-
 
|}
 
|}
Line 395: Line 864:
 
| style="vertical-align:top" | {{Option|--seed {{DT_INT}}}}
 
| style="vertical-align:top" | {{Option|--seed {{DT_INT}}}}
 
| style="vertical-align:top" | Initialises the random number generator with the given value; ''default: '''23423'''''
 
| style="vertical-align:top" | Initialises the random number generator with the given value; ''default: '''23423'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--thread-rngs {{DT_INT}}}}
 +
| style="vertical-align:top" | Number of pre-allocated random number generators to ensure repeatable multi-threaded simulations (should be at least the number of threads for repeatable simulations).; ''default: '''64'''''
 
|-
 
|-
 
|}
 
|}
Line 404: Line 876:
 
! style="background:#ddffdd; vertical-align:top" | Description
 
! style="background:#ddffdd; vertical-align:top" | Description
 
|-
 
|-
| style="vertical-align:top" | {{Option|--gui-settings-file {{DT_FILE}}}}
+
| style="vertical-align:top" | {{Option|-g {{DT_FILE}}}}<br/> {{Option|--gui-settings-file {{DT_FILE}}}}
 
| style="vertical-align:top" | Load visualisation settings from FILE
 
| style="vertical-align:top" | Load visualisation settings from FILE
 
|-
 
|-
Line 412: Line 884:
 
| style="vertical-align:top" | {{Option|-G {{DT_BOOL}}}}<br/> {{Option|--game {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|-G {{DT_BOOL}}}}<br/> {{Option|--game {{DT_BOOL}}}}
 
| style="vertical-align:top" | Start the GUI in gaming mode; ''default: '''false'''''
 
| style="vertical-align:top" | Start the GUI in gaming mode; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--game.mode {{DT_STR}}}}
 +
| style="vertical-align:top" | Select the game type ('tls', 'drt'); ''default: '''tls'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-S {{DT_BOOL}}}}<br/> {{Option|--start {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|-S {{DT_BOOL}}}}<br/> {{Option|--start {{DT_BOOL}}}}
 
| style="vertical-align:top" | Start the simulation after loading; ''default: '''false'''''
 
| style="vertical-align:top" | Start the simulation after loading; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|-B {{DT_STR}}}}<br/> {{Option|--breakpoints {{DT_STR}}}}
 +
| style="vertical-align:top" | Use TIME[] as times when the simulation should halt
 +
|-
 +
| style="vertical-align:top" | {{Option|--edgedata-files {{DT_FILE}}}}
 +
| style="vertical-align:top" | Load edge/lane weights for visualization from FILE
 +
|-
 +
| style="vertical-align:top" | {{Option|-D {{DT_BOOL}}}}<br/> {{Option|--demo {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Restart the simulation after ending (demo mode); ''default: '''false'''''
 
|-
 
|-
 
| style="vertical-align:top" | {{Option|-T {{DT_BOOL}}}}<br/> {{Option|--disable-textures {{DT_BOOL}}}}
 
| style="vertical-align:top" | {{Option|-T {{DT_BOOL}}}}<br/> {{Option|--disable-textures {{DT_BOOL}}}}
 
| style="vertical-align:top" | Do not load background pictures; ''default: '''false'''''
 
| style="vertical-align:top" | Do not load background pictures; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--registry-viewport {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Load current viewport from registry; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--window-size {{DT_STR}}}}
 +
| style="vertical-align:top" | Create initial window with the given x,y size
 +
|-
 +
| style="vertical-align:top" | {{Option|--window-pos {{DT_STR}}}}
 +
| style="vertical-align:top" | Create initial window at the given x,y position
 +
|-
 +
| style="vertical-align:top" | {{Option|--tracker-interval {{DT_FLOAT}}}}
 +
| style="vertical-align:top" | The aggregation period for value tracker windows; ''default: '''1'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--osg-view {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Start with an OpenSceneGraph view instead of the regular 2D view; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--gui-testing {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable ovelay for screen recognition; ''default: '''false'''''
 +
|-
 +
| style="vertical-align:top" | {{Option|--gui-testing-debug {{DT_BOOL}}}}
 +
| style="vertical-align:top" | Enable output messages during GUI-Testing; ''default: '''false'''''
 
|-
 
|-
 
|}
 
|}
Line 425: Line 930:
  
 
This is of particular importance in regard to files loaded with the options {{Option|--route-files {{DT_FILE}}}} and {{Option|--additional-files {{DT_FILE}}}}.
 
This is of particular importance in regard to files loaded with the options {{Option|--route-files {{DT_FILE}}}} and {{Option|--additional-files {{DT_FILE}}}}.
The most important feature of the option {{Option|--route-files {{DT_FILE}}}} is that it loads the files incrementally thus saving memory.
+
The most important feature of the option {{Option|--route-files {{DT_FILE}}}} is that it loads the files incrementally thus saving memory. However, this means vehicles and flows must be sorted by their {{XML|departure}} and {{XML|begin}} times.
The option {{Option|--additional-files {{DT_FILE}}}} is handled before option {{Option|--route-files {{DT_FILE}}}} and the given files are fully loaded before the simulation starts. Some objects  must be available at the start of the simulation (such as output objects) and thus need to be loaded with this option, but is also useful for loading things referenced by route files. (Note, that all items which can be put into a ''route-file'' can also be put into an ''additional-file''.
+
 
When multiple files are given as a comma-separated list, they are loaded from left to right.  
+
The option {{Option|--additional-files {{DT_FILE}}}} is handled before option {{Option|--route-files {{DT_FILE}}}} and the given files are fully loaded before the simulation starts. All items which can be put into a ''route-file'' can also be put into an ''additional-file'' (no vehicle sorting is necessary).
 +
Some objects  must be available at the start of the simulation (such as output objects) and thus need to be loaded with this option, but is also useful for loading things referenced by route files such as {{XML|<vType>}}-elements, named {{XML|<route>}} elements or {{XML|<routeDistribution>}}.  
 +
 
 +
When multiple files are given as a comma-separated list, they are loaded from left to right.
  
 
=Format of additional files=
 
=Format of additional files=
Files loaded with the option {{Option|--additional-files {{DT_FILE}}}} may included a wide range of network elements such as [[Simulation/Traffic_Lights|traffic light programs]], [[Simulation/Output/Induction_Loops_Detectors_%28E1%29|detector definitions]], [[Simulation/Variable_Speed_Signs|variable speed signs]] and [[Simulation/Public_Transport|bus stops]]. Also, any element permitted in a route file such as [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Vehicle_Types|vTypes]], [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Routes|routes]] and [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Vehicles_and_Routes|vehicles]] can be added. All elements may be put into the same additional file or they may be grouped into multiple files as convenient.
+
Files loaded with the option {{Option|--additional-files {{DT_FILE}}}} may included a wide range of network elements such as [[Simulation/Traffic_Lights|traffic light programs]], [[Simulation/Output/Induction_Loops_Detectors_%28E1%29|detector definitions]], [[Simulation/Variable_Speed_Signs|variable speed signs]] and [[Simulation/Public_Transport|bus stops]]. These files are also used to configure simulation outputs such as [[Simulation/Output#values_for_edges_or_lanes|edge-based traffic measures]] or [[Simulation/Output#traffic_lights-based_information|traffic light switching information]].
 +
Furthermore, any element permitted in a route file such as [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Vehicle_Types|vTypes]], [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Routes|routes]] and [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Vehicles_and_Routes|vehicles]] can be added. All elements may be put into the same additional file or they may be grouped into multiple files as convenient.
  
 
The additional file always needs a top level tag with arbitrary name (''additional'' is customary). An example file is given below:
 
The additional file always needs a top level tag with arbitrary name (''additional'' is customary). An example file is given below:
  
<additional>
+
  <additional>
 
     <inductionLoop id="myLoop1" lane="foo_0" pos="42" freq="900" file="out.xml"/>
 
     <inductionLoop id="myLoop1" lane="foo_0" pos="42" freq="900" file="out.xml"/>
 
     <inductionLoop id="myLoop2" lane="foo_2" pos="42" freq="900" file="out.xml"/>
 
     <inductionLoop id="myLoop2" lane="foo_2" pos="42" freq="900" file="out.xml"/>
Line 441: Line 950:
 
   
 
   
 
     <vType id="bus" maxSpeed="20" length="12"/>
 
     <vType id="bus" maxSpeed="20" length="12"/>
</additional>
+
  </additional>
 
 
 
 
=Insertion of vehicles=
 
Vehicles are inserted into the simulation at the time of their departure (or with a slight delay if the option {{Option|--random-depart-offset}} is used). If there is insufficient space for inserting the vehicle at that time it is put into an insertion queue and insertion is repeatedly attempted in subsequent simulation steps. If the option {{Option|--max-depart-delay {{DT_TIME}}}} is used, vehicles are discarded after {{DT_TIME}} seconds.
 
 
 
There are two methods for inserting vehicles into the simulation:
 
# try to insert every vehicle in every simulation step
 
# for every edge with vehicles to insert, abort trying to insert vehicles after one of the vehicles could not be inserted
 
 
 
In an uncongested networks these methods behave similar but in a congested network with lots of vehicles which cannot be inserted variant 2) is much faster.
 
In older version of sumo 1) was the default and one could switch to 2) using the option {{Option|--sloppy-insert}}
 
Since version 0.18.0, variant 2) is the default and one may switch to 1) using the option {{Option|--eager-insert}}.
 
  
 
=Subtopics=
 
=Subtopics=
* [[Simulation/Shapes|Using additional Polygons and POIs within the Simulation]]
+
* [[SUMO_User_Documentation#Simulation|General topics]]
 
+
* [[SUMO_User_Documentation#Traffic_Management_and_Other_Structures]]
 +
* [[SUMO_User_Documentation#Traffic_Modes]]
 +
* [[SUMO_User_Documentation#Additional_Features]]
 +
* [[SUMO_User_Documentation#Model_details]]
 +
* [[SUMO_User_Documentation#Common_Problems]]
  
 
------
 
------
  
 
[[Category:ApplicationDescription]]
 
[[Category:ApplicationDescription]]

Latest revision as of 12:09, 19 August 2019

From 30.000 feet

SUMO is the simulation itself; it is a microscopic, space-continuous, and time-discrete traffic flow simulation.

Purpose: Simulates a defined scenario
System: portable (Linux/Windows is tested); runs on command line
Input (mandatory):
A) a road network as generated via NETCONVERT or NETGENERATE, see Building Networks
B) a set of routes (as generated by DUAROUTER, JTRROUTER, DFROUTER, or ACTIVITYGEN, see also Definition of Vehicles, Vehicle Types, and Routes)
Input (optional): Additional definitions of traffic lights, variable speed signs, output detectors etc.
Output: SUMO allows to generate a wide set of outputs; visualization is done using SUMO-GUI
Programming Language: C++

Usage Description

For a brief overview see Simulation/Basic_Definition. Model details and feature documentation can be found at Simulation topics.

Options

You may use a XML schema definition file for setting up a SUMO configuration: sumoConfiguration.xsd.

Configuration

Option Description
-c <FILE>
--configuration-file <FILE>
Loads the named config on startup
-C <FILE>
--save-configuration <FILE>
Saves current configuration into FILE
--save-template <FILE> Saves a configuration template (empty) into FILE
--save-schema <FILE> Saves the configuration schema into FILE
--save-commented <BOOL> Adds comments to saved template, configuration, or schema; default: false

Input

Option Description
-n <FILE>
--net-file <FILE>
Load road network description from FILE
-r <FILE>
--route-files <FILE>
Load routes descriptions from FILE(s)
-a <FILE>
--additional-files <FILE>
Load further descriptions from FILE(s)
-w <FILE>
--weight-files <FILE>
Load edge/lane weights for online rerouting from FILE
-x <STRING>
--weight-attribute <STRING>
Name of the xml attribute which gives the edge weight; default: traveltime
--load-state <FILE> Loads a network state from FILE
--load-state.offset <TIME> Shifts all times loaded from a saved state by the given offset; default: 0
--load-state.remove-vehicles <STRING> Removes vehicles with the given IDs from the loaded state

Output

Option Description
--write-license <BOOL> Include license info into every output file; default: false
--output-prefix <STRING> Prefix which is applied to all output files. The special string 'TIME' is replaced by the current time.
--precision <INT> Defines the number of digits after the comma for floating point output; default: 2
--precision.geo <INT> Defines the number of digits after the comma for lon,lat output; default: 6
-H <BOOL>
--human-readable-time <BOOL>
Write time values as hour:minute:second or day:hour:minute:second rathern than seconds; default: false
--netstate-dump <FILE> Save complete network states into FILE
--netstate-dump.empty-edges <BOOL> Write also empty edges completely when dumping; default: false
--netstate-dump.precision <INT> Write positions and speeds with the given precision (default 2); default: 2
--emission-output <FILE> Save the emission values of each vehicle
--emission-output.precision <INT> Write emission values with the given precision (default 2); default: 2
--battery-output <FILE> Save the battery values of each vehicle
--battery-output.precision <INT> Write battery values with the given precision (default 2); default: 2
--chargingstations-output <FILE> Write data of charging stations
--fcd-output <FILE> Save the Floating Car Data
--fcd-output.geo <BOOL> Save the Floating Car Data using geo-coordinates (lon/lat); default: false
--fcd-output.signals <BOOL> Add the vehicle signal state to the FCD output (brake lights etc.); default: false
--fcd-output.distance <BOOL> Add kilometrage to the FCD output (linear referencing); default: false
--fcd-output.filter-edges.input-file <FILE> Restrict fcd output to the edge selection from the given input file
--full-output <FILE> Save a lot of information for each timestep (very redundant)
--queue-output <FILE> Save the vehicle queues at the junctions (experimental)
--vtk-output <FILE> Save complete vehicle positions inclusive speed values in the VTK Format (usage: /path/out will produce /path/out_$TIMESTEP$.vtp files)
--amitran-output <FILE> Save the vehicle trajectories in the Amitran format
--summary-output <FILE> Save aggregated vehicle departure info into FILE
--tripinfo-output <FILE> Save single vehicle trip info into FILE
--tripinfo-output.write-unfinished <BOOL> Write tripinfo output for vehicles which have not arrived at simulation end; default: false
--vehroute-output <FILE> Save single vehicle route info into FILE
--vehroute-output.exit-times <BOOL> Write the exit times for all edges; default: false
--vehroute-output.last-route <BOOL> Write the last route only; default: false
--vehroute-output.sorted <BOOL> Sorts the output by departure time; default: false
--vehroute-output.dua <BOOL> Write the output in the duarouter alternatives style; default: false
--vehroute-output.cost <BOOL> Write costs for all routes; default: false
--vehroute-output.intended-depart <BOOL> Write the output with the intended instead of the real departure time; default: false
--vehroute-output.route-length <BOOL> Include total route length in the output; default: false
--vehroute-output.write-unfinished <BOOL> Write vehroute output for vehicles which have not arrived at simulation end; default: false
--vehroute-output.skip-ptlines <BOOL> Skip vehroute output for public transport vehicles; default: false
--vehroute-output.incomplete <BOOL> Include invalid routes and route stubs in vehroute output; default: false
--link-output <FILE> Save links states into FILE
--railsignal-block-output <FILE> Save railsignal-blocks into FILE
--bt-output <FILE> Save bluetooth visibilities into FILE (in conjunction with device.btreceiver and device.btsender)
--lanechange-output <FILE> Record lane changes and their motivations for all vehicles into FILE
--lanechange-output.started <BOOL> Record start of lane change manoeuvres; default: false
--lanechange-output.ended <BOOL> Record end of lane change manoeuvres; default: false
--stop-output <FILE> Record stops and loading/unloading of passenger and containers for all vehicles into FILE
--save-state.times {{DT_INT[]}} Use INT[] as times at which a network state written
--save-state.period <TIME> save state repeatedly after TIME period; default: -1
--save-state.prefix <FILE> Prefix for network states; default: state
--save-state.suffix <STRING> Suffix for network states (.sbx or .xml); default: .sbx
--save-state.files <FILE> Files for network states

Time

Option Description
-b <TIME>
--begin <TIME>
Defines the begin time in seconds; The simulation starts at this time; default: 0
-e <TIME>
--end <TIME>
Defines the end time in seconds; The simulation ends at this time; default: -1
--step-length <TIME> Defines the step duration in seconds; default: 1

Processing

Option Description
--step-method.ballistic <BOOL> Whether to use ballistic method for the positional update of vehicles (default is a semi-implicit Euler method).; default: false
--threads <INT> Defines the number of threads for parallel simulation; default: 1
--lateral-resolution <FLOAT> Defines the resolution in m when handling lateral positioning within a lane (with -1 all vehicles drive at the center of their lane; default: -1
-s <TIME>
--route-steps <TIME>
Load routes for the next number of seconds ahead; default: 200
--no-internal-links <BOOL> Disable (junction) internal links; default: false
--ignore-junction-blocker <TIME> Ignore vehicles which block the junction after they have been standing for SECONDS (-1 means never ignore); default: -1
--ignore-route-errors <BOOL> (1) Do not check whether routes are connected. (2) Allow inserting a vehicle in a situation which requires emergency braking.; default: false
--ignore-accidents <BOOL> Do not check whether accidents occur; default: false
--collision.action <STRING> How to deal with collisions: [none,warn,teleport,remove]; default: teleport
--collision.stoptime <TIME> Let vehicle stop for TIME before performing collision.action (except for action 'none'); default: 0
--collision.check-junctions <BOOL> Enables collisions checks on junctions; default: false
--collision.mingap-factor <FLOAT> Sets the fraction of minGap that must be maintained to avoid collision detection. If a negative value is given, the carFollowModel parameter is used; default: -1
--max-num-vehicles <INT> Delay vehicle insertion to stay within the given maximum number; default: -1
--max-num-teleports <INT> Abort the simulation if the given maximum number of teleports is exceeded; default: -1
--scale <FLOAT> Scale demand by the given factor (by discarding or duplicating vehicles); default: 1
--time-to-teleport <TIME> Specify how long a vehicle may wait until being teleported, defaults to 300, non-positive values disable teleporting; default: 300
--time-to-teleport.highways <TIME> The waiting time after which vehicles on a fast road (speed > 69m/s) are teleported if they are on a non-continuing lane; default: 0
--waiting-time-memory <TIME> Length of time interval, over which accumulated waiting time is taken into account (default is 100s.); default: 100
--max-depart-delay <TIME> How long vehicles wait for departure before being skipped, defaults to -1 which means vehicles are never skipped; default: -1
--sloppy-insert <BOOL> Whether insertion on an edge shall not be repeated in same step once failed; default: false
--eager-insert <BOOL> Whether each vehicle is checked separately for insertion on an edge; default: false
--random-depart-offset <TIME> Each vehicle receives a random offset to its depart value drawn uniformly from [0, TIME]; default: 0
--lanechange.duration <TIME> Duration of a lane change maneuver (default 0); default: 0
--lanechange.overtake-right <BOOL> Whether overtaking on the right on motorways is permitted; default: false
--tls.all-off <BOOL> Switches off all traffic lights.; default: false
--tls.actuated.show-detectors <BOOL> Sets default visibility for actuation detectors; default: false
--tls.delay_based.detector-range <FLOAT> Sets default range for detecting delayed vehicles; default: 100
--time-to-impatience <TIME> Specify how long a vehicle may wait until impatience grows from 0 to 1, defaults to 300, non-positive values disable impatience growth; default: 300
--default.action-step-length <FLOAT> Length of the default interval length between action points for the car-following and lane-change models (in seconds). If not specified, the simulation step-length is used per default. Vehicle- or VType-specific settings override the default. Must be a multiple of the simulation step-length.; default: 0
--default.carfollowmodel <STRING> Select default car following model (Krauss, IDM, ...); default: Krauss
--default.speeddev <FLOAT> Select default speed deviation. A negative value implies vClass specific defaults (0.1 for the default passenger class; default: -1
--default.emergencydecel <STRING> Select default emergencyDecel value among ('decel', 'default', FLOAT) which sets the value either to the same as the deceleration value, a vClass-class specific default or the given FLOAT in m/s^2; default: default
--emergencydecel.warning-threshold <FLOAT> Sets the fraction of emergency decel capability that must be used to trigger a warning.; default: 1
--pedestrian.model <STRING> Select among pedestrian models ['nonInteracting', 'striping', 'remote']; default: striping
--pedestrian.striping.stripe-width <FLOAT> Width of parallel stripes for segmenting a sidewalk (meters) for use with model 'striping'; default: 0.64
--pedestrian.striping.dawdling <FLOAT> Factor for random slow-downs [0,1] for use with model 'striping'; default: 0.2
--pedestrian.striping.jamtime <TIME> Time in seconds after which pedestrians start squeezing through a jam when using model 'striping' (non-positive values disable squeezing); default: 300
--pedestrian.striping.jamtime.crossing <TIME> Time in seconds after which pedestrians start squeezing through a jam while on a pedestrian crossing when using model 'striping' (non-positive values disable squeezing); default: 10
--pedestrian.remote.address <STRING> The address (host:port) of the external simulation; default: localhost:9000
--ride.stop-tolerance <FLOAT> Tolerance to apply when matching pedestrian and vehicle positions on boarding at individual stops; default: 10

Routing

Option Description
--routing-algorithm <STRING> Select among routing algorithms ['dijkstra', 'astar', 'CH', 'CHWrapper']; default: dijkstra
--weights.random-factor <FLOAT> Edge weights for routing are dynamically disturbed by a random factor drawn uniformly from [1,FLOAT); default: 1
--weights.minor-penalty <FLOAT> Apply the given time penalty when computing minimum routing costs for minor-link internal lanes; default: 1.5
--astar.all-distances <FILE> Initialize lookup table for astar from the given file (generated by marouter --all-pairs-output)
--astar.landmark-distances <FILE> Initialize lookup table for astar ALT-variant from the given file
--persontrip.walkfactor <FLOAT> Use FLOAT as a factor on pedestrian maximum speed during intermodal routing; default: 0.75
--persontrip.transfer.car-walk <STRING> Where are mode changes from car to walking allowed (possible values: 'parkingAreas', 'ptStops', 'allJunctions' and combinations); default: parkingAreas
--device.rerouting.probability <FLOAT> The probability for a vehicle to have a 'rerouting' device; default: -1
--device.rerouting.explicit <STRING> Assign a 'rerouting' device to named vehicles
--device.rerouting.deterministic <BOOL> The 'rerouting' devices are set deterministic using a fraction of 1000; default: false
--device.rerouting.period <TIME> The period with which the vehicle shall be rerouted; default: 0
--device.rerouting.pre-period <TIME> The rerouting period before depart; default: 60
--device.rerouting.adaptation-weight <FLOAT> The weight of prior edge weights for exponential moving average; default: 0
--device.rerouting.adaptation-steps <INT> The number of steps for moving average weight of prior edge weights; default: 180
--device.rerouting.adaptation-interval <TIME> The interval for updating the edge weights; default: 1
--device.rerouting.with-taz <BOOL> Use zones (districts) as routing start- and endpoints; default: false
--device.rerouting.init-with-loaded-weights <BOOL> Use weight files given with option --weight-files for initializing edge weights; default: false
--device.rerouting.threads <INT> The number of parallel execution threads used for rerouting; default: 0
--device.rerouting.synchronize <BOOL> Let rerouting happen at the same time for all vehicles; default: false
--device.rerouting.output <FILE> Save adapting weights to FILE
--person-device.rerouting.probability <FLOAT> The probability for a person to have a 'rerouting' device; default: -1
--person-device.rerouting.explicit <STRING> Assign a 'rerouting' device to named persons
--person-device.rerouting.deterministic <BOOL> The 'rerouting' devices are set deterministic using a fraction of 1000; default: false
--person-device.rerouting.period <TIME> The period with which the person shall be rerouted; default: 0

Report

Option Description
-v <BOOL>
--verbose <BOOL>
Switches to verbose output; default: false
--print-options <BOOL> Prints option values before processing; default: false
-? <BOOL>
--help <BOOL>
Prints this screen or selected topics; default: false
-V <BOOL>
--version <BOOL>
Prints the current version; default: false
-X <STRING>
--xml-validation <STRING>
Set schema validation scheme of XML inputs ("never", "auto" or "always"); default: auto
--xml-validation.net <STRING> Set schema validation scheme of SUMO network inputs ("never", "auto" or "always"); default: never
-W <BOOL>
--no-warnings <BOOL>
Disables output of warnings; default: false
-l <FILE>
--log <FILE>
Writes all messages to FILE (implies verbose)
--message-log <FILE> Writes all non-error messages to FILE (implies verbose)
--error-log <FILE> Writes all warnings and errors to FILE
--duration-log.disable <BOOL> Disable performance reports for individual simulation steps; default: false
--duration-log.statistics <BOOL> Enable statistics on vehicle trips; default: false
--no-step-log <BOOL> Disable console output of current simulation step; default: false

Emissions

Option Description
--phemlight-path <FILE> Determines where to load PHEMlight definitions from.; default: ./PHEMlight/
--device.emissions.probability <FLOAT> The probability for a vehicle to have a 'emissions' device; default: -1
--device.emissions.explicit <STRING> Assign a 'emissions' device to named vehicles
--device.emissions.deterministic <BOOL> The 'emissions' devices are set deterministic using a fraction of 1000; default: false

Communication

Option Description
--device.btreceiver.probability <FLOAT> The probability for a vehicle to have a 'btreceiver' device; default: -1
--device.btreceiver.explicit <STRING> Assign a 'btreceiver' device to named vehicles
--device.btreceiver.deterministic <BOOL> The 'btreceiver' devices are set deterministic using a fraction of 1000; default: false
--device.btreceiver.range <FLOAT> The range of the bt receiver; default: 300
--device.btreceiver.all-recognitions <BOOL> Whether all recognition point shall be written; default: false
--device.btreceiver.offtime <FLOAT> The offtime used for calculating detection probability (in seconds); default: 0.64
--device.btsender.probability <FLOAT> The probability for a vehicle to have a 'btsender' device; default: -1
--device.btsender.explicit <STRING> Assign a 'btsender' device to named vehicles
--device.btsender.deterministic <BOOL> The 'btsender' devices are set deterministic using a fraction of 1000; default: false

Battery

Option Description
--device.battery.probability <FLOAT> The probability for a vehicle to have a 'battery' device; default: -1
--device.battery.explicit <STRING> Assign a 'battery' device to named vehicles
--device.battery.deterministic <BOOL> The 'battery' devices are set deterministic using a fraction of 1000; default: false

Example Device

Option Description
--device.example.probability <FLOAT> The probability for a vehicle to have a 'example' device; default: -1
--device.example.explicit <STRING> Assign a 'example' device to named vehicles
--device.example.deterministic <BOOL> The 'example' devices are set deterministic using a fraction of 1000; default: false
--device.example.parameter <FLOAT> An exemplary parameter which can be used by all instances of the example device; default: 0

Ssm Device

Option Description
--device.ssm.probability <FLOAT> The probability for a vehicle to have a 'ssm' device; default: -1
--device.ssm.explicit <STRING> Assign a 'ssm' device to named vehicles
--device.ssm.deterministic <BOOL> The 'ssm' devices are set deterministic using a fraction of 1000; default: false
--device.ssm.measures <STRING> Specifies which measures will be logged (as a space separated sequence of IDs in ('TTC', 'DRAC', 'PET')).
--device.ssm.thresholds <STRING> Specifies thresholds corresponding to the specified measures (see documentation and watch the order!). Only events exceeding the thresholds will be logged.
--device.ssm.trajectories <BOOL> Specifies whether trajectories will be logged (if false, only the extremal values and times are reported, this is the default).
--device.ssm.range <FLOAT> Specifies the detection range in meters (default is 50.00m.). For vehicles below this distance from the equipped vehicle, SSM values are traced.
--device.ssm.extratime <FLOAT> Specifies the time in seconds to be logged after a conflict is over (default is 5.00secs.). Required >0 if PET is to be calculated for crossing conflicts.
--device.ssm.file <STRING> Give a global default filename for the SSM output.
--device.ssm.geo <BOOL> Whether to use coordinates of the original reference system in output (default is false).

Toc Device

Option Description
--device.toc.probability <FLOAT> The probability for a vehicle to have a 'toc' device; default: -1
--device.toc.explicit <STRING> Assign a 'toc' device to named vehicles
--device.toc.deterministic <BOOL> The 'toc' devices are set deterministic using a fraction of 1000; default: false
--device.toc.manualType <STRING> Vehicle type for manual driving regime.
--device.toc.automatedType <STRING> Vehicle type for automated driving regime.
--device.toc.responseTime <FLOAT> Average response time needed by a driver to take back control.; default: -1
--device.toc.recoveryRate <FLOAT> Recovery rate for the driver's awareness after a ToC.; default: 0.1
--device.toc.lcAbstinence <FLOAT> Attention level below which a driver restrains from performing lane changes (value in [0,1]).; default: 0
--device.toc.initialAwareness <FLOAT> Average awareness a driver has initially after a ToC (value in [0,1]).; default: 0.5
--device.toc.mrmDecel <FLOAT> Deceleration rate applied during a 'minimum risk maneuver'.; default: 1.5
--device.toc.dynamicToCThreshold <FLOAT> Time, which the vehicle requires to have ahead to continue in automated mode. The default value of 0 indicates no dynamic triggering of ToCs.; default: 0
--device.toc.dynamicMRMProbability <FLOAT> Probability that a dynamically triggered TOR is not answered in time.; default: 0.05
--device.toc.mrmKeepRight <BOOL> If true, the vehicle tries to change to the right during an MRM.; default: false
--device.toc.maxPreparationAccel <FLOAT> Maximal acceleration that may be applied during the ToC preparation phase.; default: 0
--device.toc.ogNewTimeHeadway <FLOAT> Timegap for ToC preparation phase.; default: -1
--device.toc.ogNewSpaceHeadway <FLOAT> Additional spacing for ToC preparation phase.; default: -1
--device.toc.ogMaxDecel <FLOAT> Maximal deceleration applied for establishing increased gap in ToC preparation phase.; default: -1
--device.toc.ogChangeRate <FLOAT> Rate of adaptation towards the increased headway during ToC preparation.; default: -1
--device.toc.useColorScheme <BOOL> Whether a coloring scheme shall by applied to indicate the different ToC stages.; default: true
--device.toc.file <STRING> Switches on output by specifying an output filename.

Driver State Device

Option Description
--device.driverstate.probability <FLOAT> The probability for a vehicle to have a 'driverstate' device; default: -1
--device.driverstate.explicit <STRING> Assign a 'driverstate' device to named vehicles
--device.driverstate.deterministic <BOOL> The 'driverstate' devices are set deterministic using a fraction of 1000; default: false
--device.driverstate.initialAwareness <FLOAT> Initial value assigned to the driver's awareness.; default: 1
--device.driverstate.errorTimeScaleCoefficient <FLOAT> Time scale for the error process.; default: 100
--device.driverstate.errorNoiseIntensityCoefficient <FLOAT> Noise intensity driving the error process.; default: 0.2
--device.driverstate.speedDifferenceErrorCoefficient <FLOAT> General scaling coefficient for applying the error to the perceived speed difference (error also scales with distance).; default: 0.15
--device.driverstate.headwayErrorCoefficient <FLOAT> General scaling coefficient for applying the error to the perceived distance (error also scales with distance).; default: 0.75
--device.driverstate.speedDifferenceChangePerceptionThreshold <FLOAT> Base threshold for recognizing changes in the speed difference (threshold also scales with distance).; default: 0.1
--device.driverstate.headwayChangePerceptionThreshold <FLOAT> Base threshold for recognizing changes in the headway (threshold also scales with distance).; default: 0.1
--device.driverstate.minAwareness <FLOAT> Minimal admissible value for the driver's awareness.; default: 0.1
--device.driverstate.maximalReactionTime <FLOAT> Maximal reaction time (~action step length) induced by decreased awareness level (reached for awareness=minAwareness).; default: -1

Bluelight Device

Option Description
--device.bluelight.probability <FLOAT> The probability for a vehicle to have a 'bluelight' device; default: -1
--device.bluelight.explicit <STRING> Assign a 'bluelight' device to named vehicles
--device.bluelight.deterministic <BOOL> The 'bluelight' devices are set deterministic using a fraction of 1000; default: false
--device.bluelight.parameter <FLOAT> An exemplary parameter which can be used by all instances of the example device; default: 0

Fcd Device

Option Description
--device.fcd.probability <FLOAT> The probability for a vehicle to have a 'fcd' device; default: -1
--device.fcd.explicit <STRING> Assign a 'fcd' device to named vehicles
--device.fcd.deterministic <BOOL> The 'fcd' devices are set deterministic using a fraction of 1000; default: false
--device.fcd.period <STRING> Recording period for FCD-data; default: 0
--person-device.fcd.probability <FLOAT> The probability for a person to have a 'fcd' device; default: -1
--person-device.fcd.explicit <STRING> Assign a 'fcd' device to named persons
--person-device.fcd.deterministic <BOOL> The 'fcd' devices are set deterministic using a fraction of 1000; default: false
--person-device.fcd.period <STRING> Recording period for FCD-data; default: 0

Traci Server

Option Description
--remote-port <INT> Enables TraCI Server if set; default: 0
--num-clients <INT> Expected number of connecting clients; default: 1

Mesoscopic

Option Description
--mesosim <BOOL> Enables mesoscopic simulation; default: false
--meso-edgelength <FLOAT> Length of an edge segment in mesoscopic simulation; default: 98
--meso-tauff <TIME> Factor for calculating the net free-free headway time; default: 1.13
--meso-taufj <TIME> Factor for calculating the net free-jam headway time; default: 1.13
--meso-taujf <TIME> Factor for calculating the jam-free headway time; default: 1.73
--meso-taujj <TIME> Factor for calculating the jam-jam headway time; default: 1.4
--meso-jam-threshold <FLOAT> Minimum percentage of occupied space to consider a segment jammed. A negative argument causes thresholds to be computed based on edge speed and tauff (default); default: -1
--meso-multi-queue <BOOL> Enable multiple queues at edge ends; default: true
--meso-junction-control <BOOL> Enable mesoscopic traffic light and priority junction handling; default: false
--meso-junction-control.limited <BOOL> Enable mesoscopic traffic light and priority junction handling for saturated links. This prevents faulty traffic lights from hindering flow in low-traffic situations; default: false
--meso-tls-penalty <FLOAT> Apply scaled time penalties when driving across tls controlled junctions based on green split instead of checking actual phases; default: 0
--meso-minor-penalty <TIME> Apply fixed time penalty when driving across a minor link. When using --meso-junction-control.limited, the penalty is not applied whenever limited control is active.; default: 0
--meso-overtaking <BOOL> Enable mesoscopic overtaking; default: false
--meso-recheck <TIME> Time interval for rechecking insertion into the next segment after failure; default: 0

Random Number

Option Description
--random <BOOL> Initialises the random number generator with the current system time; default: false
--seed <INT> Initialises the random number generator with the given value; default: 23423
--thread-rngs <INT> Number of pre-allocated random number generators to ensure repeatable multi-threaded simulations (should be at least the number of threads for repeatable simulations).; default: 64

Gui Only

Option Description
-g <FILE>
--gui-settings-file <FILE>
Load visualisation settings from FILE
-Q <BOOL>
--quit-on-end <BOOL>
Quits the GUI when the simulation stops; default: false
-G <BOOL>
--game <BOOL>
Start the GUI in gaming mode; default: false
--game.mode <STRING> Select the game type ('tls', 'drt'); default: tls
-S <BOOL>
--start <BOOL>
Start the simulation after loading; default: false
-B <STRING>
--breakpoints <STRING>
Use TIME[] as times when the simulation should halt
--edgedata-files <FILE> Load edge/lane weights for visualization from FILE
-D <BOOL>
--demo <BOOL>
Restart the simulation after ending (demo mode); default: false
-T <BOOL>
--disable-textures <BOOL>
Do not load background pictures; default: false
--registry-viewport <BOOL> Load current viewport from registry; default: false
--window-size <STRING> Create initial window with the given x,y size
--window-pos <STRING> Create initial window at the given x,y position
--tracker-interval <FLOAT> The aggregation period for value tracker windows; default: 1
--osg-view <BOOL> Start with an OpenSceneGraph view instead of the regular 2D view; default: false
--gui-testing <BOOL> Enable ovelay for screen recognition; default: false
--gui-testing-debug <BOOL> Enable output messages during GUI-Testing; default: false

Loading order of input files

Whenever a simulation object A (such as a vehicle) defined in an input file refers to another simulation object B (such as a vehicle type), the corresponding object B must be defined before A either by being put into a file that is loaded earlier, or by being put into the same file on an earlier line.

This is of particular importance in regard to files loaded with the options --route-files <FILE> and --additional-files <FILE>. The most important feature of the option --route-files <FILE> is that it loads the files incrementally thus saving memory. However, this means vehicles and flows must be sorted by their departure and begin times.

The option --additional-files <FILE> is handled before option --route-files <FILE> and the given files are fully loaded before the simulation starts. All items which can be put into a route-file can also be put into an additional-file (no vehicle sorting is necessary). Some objects must be available at the start of the simulation (such as output objects) and thus need to be loaded with this option, but is also useful for loading things referenced by route files such as <vType>-elements, named <route> elements or <routeDistribution>.

When multiple files are given as a comma-separated list, they are loaded from left to right.

Format of additional files

Files loaded with the option --additional-files <FILE> may included a wide range of network elements such as traffic light programs, detector definitions, variable speed signs and bus stops. These files are also used to configure simulation outputs such as edge-based traffic measures or traffic light switching information. Furthermore, any element permitted in a route file such as vTypes, routes and vehicles can be added. All elements may be put into the same additional file or they may be grouped into multiple files as convenient.

The additional file always needs a top level tag with arbitrary name (additional is customary). An example file is given below:

 <additional>
    <inductionLoop id="myLoop1" lane="foo_0" pos="42" freq="900" file="out.xml"/>
    <inductionLoop id="myLoop2" lane="foo_2" pos="42" freq="900" file="out.xml"/>
 
    <busStop id="station1" lane="foo_0" startPos="5" endPos="20"/>

    <vType id="bus" maxSpeed="20" length="12"/>
 </additional>

Subtopics