ECLIPSE(1)

📦
version 1.27.1 · 7 versions
, in ubuntu stonking

💅 NAME 💅

Eclipse — GUI version of the simulation SUMO. (yep bestie, this is the ECLIPSE(1) manual page, and we're about to make traffic simulation make sense 💖)

✨ SYNOPSIS ✨

sumo-gui [OPTION]*

🌸 DESCRIPTION 🌸

okay so this is Eclipse SUMO GUI 1.27.1 — the GUI version of the microscopic, multi-modal traffic simulation SUMO. It's giving main character simulation energy, no cap.

Copyright (C) 2001-2026 German Aerospace Center (DLR) and others; https://sumo.dlr.de

🎀 Configuration Options 🎀

  • -c, --configuration-file FILE — Loads the named config on startup. your "bring your own setup" moment fr fr.
  • -C, --save-configuration FILE — Saves current configuration into FILE. slay, now your setup is preserved.
  • --save-configuration.relative — Enforce relative paths when saving the configuration. keeping it portable, periodt.
  • --save-template FILE — Saves a configuration template (empty) into FILE. a lil blank canvas, bestie.
  • --save-schema FILE — Saves the configuration schema into FILE. the rules of the game, written down.
  • --save-commented — Adds comments to saved template, configuration, or schema. so helpful, so iconic.

🔌 Input Options 🔌

  • -n, --net-file FILE — Load road network description from FILE. the roads, the vibe, the whole map.
  • -r, --route-files FILE — Load routes descriptions from FILE(s). where everybody's going, bestie.
  • -a, --additional-files FILE — Load further descriptions from FILE(s). extra lore, we love it.
  • -w, --weight-files FILE — Load edge/lane weights for online rerouting from FILE. weighted decisions, highkey important.
  • -x, --weight-attribute STR — Name of the xml attribute which gives the edge weight. tell it which attribute is the main character.
  • --load-state FILE — Loads a network state from FILE. pick up where you left off, no biggie.
  • --load-state.offset TIME — Shifts all times loaded from a saved state by the given offset. time travel but make it traffic.
  • --load-state.remove-vehicles STR[] — Removes vehicles with the given IDs from the loaded state. bye bye, specific lil cars.
  • --junction-taz — Initialize a TAZ for every junction to use attributes toJunction and fromJunction. junctions get their own TAZ moment, iykyk.

📝 Output Options 📝

  • --write-license — Include license info into every output file. legal girlies rise.
  • --write-metadata — Write parsable metadata (configuration etc.) instead of comments. structured and clean, we stan.
  • --output-prefix STR — Prefix which is applied to all output files. The special string 'TIME' is replaced by the current time. timestamped slay.
  • --output-suffix STR — Suffix which is applied to all output files. The special string 'TIME' is replaced by the current time. same energy, other end.
  • --precision INT — Defines the number of digits after the comma for floating point output. decimals matter, periodt.
  • --precision.geo INT — Defines the number of digits after the comma for lon,lat output. geo precision bestie.
  • --output.compression STR — Defines the standard compression algorithm (currently only for parquet output). squeeze it, but only for parquet rn.
  • --output.format STR — Defines the standard output format if not derivable from the file name ('xml', 'csv', 'parquet'). pick your format era.
  • --output.column-header STR — How to derive column headers from attribute names ('none', 'tag', 'auto', 'plain'). headers, but make it your choice.
  • --output.column-separator STR — Separator in CSV output. commas? semicolons? you decide, bestie.
  • -H, --human-readable-time — Write time values as hour:minute:second or day:hour:minute:second rather than seconds. finally, time that reads like a clock 💅.
  • --netstate-dump FILE — Save complete network states into FILE. the whole network, every state.
  • --netstate-dump.empty-edges — Write also empty edges completely when dumping. no edge left behind.
  • --netstate-dump.precision INT — Write positions and speeds with the given precision (default 2). default is 2, keep it cute.
  • --emission-output FILE — Save the emission values of each vehicle. emissions tea, spilled.
  • --emission-output.precision INT — Write emission values with the given precision (default 2). default 2 again, iconic.
  • --emission-output.geo — Save the positions in emission output using geo-coordinates (lon/lat). longitude/latitude girlies, this is for you.
  • --emission-output.step-scaled — Write emission values scaled to the step length rather than as per-second values. step-scaled, not per-second, got it.
  • --emission-output.attributes STR[] — List attributes that should be included in the emission output. choose your faves.
  • --battery-output FILE — Save the battery values of each vehicle. battery charge, but in a file.
  • --battery-output.precision INT — Write battery values with the given precision (default 2). default 2, obviously.
  • --elechybrid-output FILE — Save the elecHybrid values of each vehicle. elecHybrid besties stand up.
  • --elechybrid-output.precision INT — Write elecHybrid values with the given precision (default 2). default 2, no cap.
  • --elechybrid-output.aggregated — Write elecHybrid values into one aggregated file. one file to rule them all.
  • --chargingstations-output FILE — Write data of charging stations. charging station lore.
  • --chargingstations-output.aggregated — Write aggregated charging event data instead of single time steps. aggregated > one-by-one, periodt.
  • --chargingstations-output.aggregated.write-unfinished — Write aggregated charging event data for vehicles which have not arrived at simulation end. unfinished but still counted, we love.
  • --overheadwiresegments-output FILE — Write data of overhead wire segments. wire segment data, slay.
  • --substations-output FILE — Write data of electrical substation stations. substation station energy, literally.
  • --substations-output.precision INT — Write substation values with the given precision (default 2). default 2, always.
  • --fcd-output FILE — Save the Floating Car Data. FCD girlies, this is your moment.
  • --fcd-output.geo — Save the Floating Car Data using geo-coordinates (lon/lat). geo-coordinates, we love a map moment.
  • --fcd-output.utm — Save the Floating Car Data using utm/unshifted coordinates (x/y). utm/unshifted, x/y vibes.
  • --fcd-output.signals — Add the vehicle signal state to the FCD output (brake lights etc.). brake lights included, cute.
  • --fcd-output.distance — Add kilometrage to the FCD output (linear referencing). kilometrage, linear referencing, we're fancy.
  • --fcd-output.acceleration — Add acceleration to the FCD output. vroom vroom math.
  • --fcd-output.speed-relative — Add relative speed (vehicle speed / edge speed limit) to the FCD output. vehicle speed divided by edge speed limit, iykyk.
  • --fcd-output.max-leader-distance FLOAT — Add leader vehicle information to the FCD output (within the given distance). leader vehicle info, but only within the given distance.
  • --fcd-output.params STR[] — Add generic parameter values to the FCD output. generic params, still important.
  • --fcd-output.filter-edges.input-file FILE — Restrict fcd output to the edge selection from the given input file. edge selection filter, bestie.
  • --fcd-output.attributes STR[] — List attributes that should be included in the FCD output. pick the attributes, choose your destiny.
  • --fcd-output.filter-shapes STR[] — List shape names that should be used to filter the FCD output. shape names as filters, iconic.
  • --fcd-output.skip-empty — Do not save data for time steps which have no vehicles / transportables. no vehicles, no transportables, no output, periodt.
  • --person-fcd-output FILE — Save fcd for persons and container to separate FILE. persons and containers get their own separate file, so valid.
  • --device.ssm.filter-edges.input-file FILE — Restrict SSM device output to the edge selection from the given input file. SSM output edge selection, got it.
  • --full-output FILE — Save a lot of information for each timestep (very redundant). a lot. very redundant. but sometimes you need the whole novel.
  • --queue-output FILE — Save the vehicle queues at the junctions (experimental). experimental queue energy, handle with care.
  • --queue-output.period TIME — Save vehicle queues with the given period. every given period, queue check.
  • --vtk-output FILE — Save complete vehicle positions inclusive speed values in the VTK Format (usage: /path/out will produce /path/out_$TIMESTEP$.vtp files). VTK format, timestep files, so specific.
  • --amitran-output FILE — Save the vehicle trajectories in the Amitran format. Amitran format, we love a format moment.
  • --summary-output FILE — Save aggregated vehicle departure info into FILE. departure info, aggregated and cute.
  • --summary-output.period TIME — Save summary-output with the given period. period by period, we summarize.
  • --person-summary-output FILE — Save aggregated person counts into FILE. person counts, aggregated, slay.
  • --tripinfo-output FILE — Save single vehicle trip info into FILE. one vehicle, one trip, one file, periodt.
  • --tripinfo-output.write-unfinished — Write tripinfo output for vehicles which have not arrived at simulation end. unfinished trips still get their moment.
  • --tripinfo-output.write-undeparted — Write tripinfo output for vehicles which have not departed at simulation end because of depart delay. depart delay girlies, you're seen.
  • --personinfo-output FILE — Save personinfo and containerinfo to separate FILE. personinfo and containerinfo, separate file, we love boundaries.
  • --vehroute-output FILE — Save single vehicle route info into FILE. route info for one vehicle, bestie.
  • --vehroute-output.exit-times — Write the exit times for all edges. every edge exit time, no skips.
  • --vehroute-output.last-route — Write the last route only. just the last route, keep it simple.
  • --vehroute-output.sorted — Sorts the output by departure time. sorted by departure time, organized queen.
  • --vehroute-output.dua — Write the output in the duarouter alternatives style. duarouter alternatives style, fancy.
  • --vehroute-output.cost — Write costs for all routes. costs for all routes, budget era.
  • --vehroute-output.intended-depart — Write the output with the intended instead of the real departure time. intended > real, in this specific case.
  • --vehroute-output.route-length — Include total route length in the output. total route length, included.
  • --vehroute-output.write-unfinished — Write vehroute output for vehicles which have not arrived at simulation end. unfinished vehicles still get vehroute output.
  • --vehroute-output.skip-ptlines — Skip vehroute output for public transport vehicles. public transport vehicles get skipped here, periodt.
  • --vehroute-output.incomplete — Include invalid routes and route stubs in vehroute output. invalid routes and route stubs, included.
  • --vehroute-output.stop-edges — Include information about edges between stops. edges between stops, included.
  • --vehroute-output.speedfactor — Write the vehicle speedFactor (defaults to 'true' if departSpeed is written). defaults to 'true' if departSpeed is written, noted.
  • --vehroute-output.internal — Include internal edges in the output. internal edges, not hidden.
  • --personroute-output FILE — Save person and container routes to separate FILE. person routes and container routes, separate file, we stan.
  • --link-output FILE — Save links states into FILE. link states, saved.
  • --railsignal-block-output FILE — Save railsignal-blocks into FILE. railsignal-blocks, in a file.
  • --railsignal-vehicle-output FILE — Record entry and exit times of vehicles for railsignal blocks into FILE. entry and exit times, recorded.
  • --bt-output FILE — Save bluetooth visibilities into FILE (in conjunction with device.btreceiver and device.btsender). bluetooth visibilities, works with device.btreceiver and device.btsender.
  • --lanechange-output FILE — Record lane changes and their motivations for all vehicles into FILE. lane changes and their motivations, we need the why.
  • --lanechange-output.started — Record start of lane change manoeuvres. start recorded.
  • --lanechange-output.ended — Record end of lane change manoeuvres. end recorded.
  • --lanechange-output.xy — Record coordinates of lane change manoeuvres. x/y coordinates, recorded.
  • --stop-output FILE — Record stops and loading/unloading of passenger and containers for all vehicles into FILE. stops, loading, unloading, passengers, containers, all in one file.
  • --stop-output.write-unfinished — Write stop output for stops which have not ended at simulation end. unfinished stops still get output.
  • --collision-output FILE — Write collision information into FILE. collision info, dramatic but necessary.
  • --edgedata-output FILE — Write aggregated traffic statistics for all edges into FILE. edge traffic stats, aggregated.
  • --lanedata-output FILE — Write aggregated traffic statistics for all lanes into FILE. lane traffic stats, aggregated.
  • --statistic-output FILE — Write overall statistics into FILE. overall stats, the big picture.
  • --deadlock-output FILE — Write reports on deadlocks FILE. deadlock reports, bestie.
  • --save-state.times STR[] — Use TIME[] as times at which a network state written. network state at those times, got it.
  • --save-state.period TIME — save state repeatedly after TIME period. repeated state saving, period by period.
  • --save-state.period.keep INT — Keep only the last INT periodic state files. only the last INT, keep it tidy.
  • --save-state.prefix FILE — Prefix for network states. network state prefix, the final touch.
  • --save-state.suffix STR — the little suffix that goes on your network state files, .xml.gz or plain .xml, your call 💾
  • --save-state.files FILE — the actual files for the network states, bestie
  • --save-state.rng — save out the random number generator states too (yes, the RNG deserves its own lil snapshot 🎲)
  • --save-state.transportables — saves person and container states. warning: experimental, so it's lowkey a work in progress 🧪
  • --save-state.constraints — save those rail signal constraints ✨
  • --save-state.precision INT — how precise do we write the internal state values? give it an int. default is 2 🎯

⏰ Time Options ⏰

  • -b, --begin TIME — sets the begin time in seconds; like, the sim starts here 🕐
  • -e, --end TIME — sets the end time in seconds; the sim ends here and that's it, goodbye 👋
  • --step-length TIME — the step duration in seconds, aka how chunky each tick of time is ⏱️

🔥 Processing Options 🔥

  • --step-method.ballistic — do we use the ballistic method for the positional update of vehicles? (default is a semi-implicit Euler method, if you were wondering) 🚀
  • --extrapolate-departpos — should vehicles that depart between simulation steps extrapolate their depart position? mid-step girlies stay winning 💅
  • --threads INT — how many threads you want for parallel simulation. yes ma'am, multicore 💖
  • --lateral-resolution FLOAT — the resolution in m for handling lateral positioning inside a lane. and listen, if you pass -1 then all vehicles just drive at the center of their lane 🛣️
  • -s, --route-steps TIME — load routes for the next however-many seconds ahead 🔮
  • --no-internal-links — disables (junction) internal links 🚫
  • --ignore-junction-blocker TIME — ignore vehicles blocking the junction once they've been standing there for SECONDS. pass -1 and it means never ignore them, periodt
  • --ignore-route-errors — don't check whether routes are connected 🙈
  • --ignore-accidents — don't check whether accidents occur. no thoughts head empty ✨
  • --collision.action STR — how do we deal with collisions? options are [none,warn,teleport,remove] 💥
  • --intermodal-collision.action STR — how to deal with collisions between a vehicle and a pedestrian: [none,warn,teleport,remove] 🚶
  • --collision.stoptime TIME — let the vehicle stop for TIME before carrying out the collision action (except for action none)
  • --intermodal-collision.stoptime TIME — let the vehicle stop for TIME before the intermodal-collision action (again, except for action none)
  • --collision.check-junctions — enables collision checks on junctions ✅
  • --collision.check-junctions.mingap FLOAT — turn the sensitivity for the junction collision check up or down 🎚️
  • --collision.mingap-factor FLOAT — sets the fraction of minGap that has to be maintained to avoid collision detection. if you give it a negative value, the carFollowModel parameter gets used instead
  • --keep-after-arrival TIME — after a vehicle arrives, keep it in memory for the given TIME (so TraCI can still access it, iykyk) 🧠
  • --max-num-vehicles INT — delay vehicle insertion so you stay within the given max number 🚗
  • --max-num-persons INT — delay person insertion to stay within the given max number 🧍
  • --max-num-teleports INT — abort the whole simulation if that max number of teleports gets exceeded 💀
  • --scale FLOAT — scale demand by this factor (by discarding or duplicating vehicles) 📈
  • --scale-suffix STR — suffix added when creating ids for cloned vehicles 🏷️
  • --time-to-teleport TIME — how long a vehicle may wait before it gets teleported. defaults to 300, and non-positive values disable teleporting entirely ✨
  • --time-to-teleport.highways TIME — the waiting time after which vehicles on a fast road (speed > 69km/h) get teleported if they're sitting on a non-continuing lane
  • --time-to-teleport.highways.min-speed FLOAT — the waiting time after which vehicles on a fast road (default: speed > 69km/h) are teleported if they're on a non-continuing lane
  • --time-to-teleport.disconnected TIME — the waiting time after which vehicles with a disconnected route get teleported. negative values disable teleporting
  • --time-to-teleport.remove — should vehicles be removed after waiting too long instead of being teleported? 🗑️
  • --time-to-teleport.remove-constraint — should rail-signal-constraint-based deadlocks be cleared by removing a constraint?
  • --time-to-teleport.ride TIME — the waiting time after which persons / containers waiting for a pickup get teleported. negative values disable teleporting
  • --time-to-teleport.bidi TIME — the waiting time after which vehicles on bidirectional edges get teleported
  • --time-to-teleport.railsignal-deadlock TIME — the waiting time after which vehicles stuck in a rail-signal-based deadlock get teleported 🚂
  • --waiting-time-memory TIME — length of the time interval over which accumulated waiting time is taken into account (default is 100s.) ⌛
  • --startup-wait-threshold TIME — minimum consecutive waiting time before startupDelay gets applied
  • --max-depart-delay TIME — how long vehicles wait for departure before getting skipped. defaults to -1, which means vehicles are never skipped 👑
  • --sloppy-insert — should insertion on an edge not be repeated in the same step once it's failed?
  • --eager-insert — should each vehicle be checked separately for insertion on an edge?
  • --emergency-insert — allow inserting a vehicle in a situation that requires emergency braking 🚨 (bold move, bestie)
  • --insertion-checks STR — override the default value for the vehicle attribute insertionChecks
  • --random-depart-offset TIME — every vehicle gets a random offset added to its depart value, drawn uniformly from [0, TIME] 🎲
  • --lanechange.duration TIME — duration of a lane change maneuver (default 0) 🚙
  • --lanechange.overtake-right — is overtaking on the right on motorways permitted? 🏎️
  • --tls.all-off — switches off all traffic lights. all of them. periodt 🚦
  • --tls.actuated.show-detectors — sets the default visibility for actuation detectors 👀
  • --tls.actuated.jam-threshold FLOAT — sets the default jam-threshold parameter for all actuation detectors
  • --tls.actuated.detector-length FLOAT — sets the default detector length parameter for all actuation detectors
  • --tls.delay_based.detector-range FLOAT — sets the default range for detecting delayed vehicles
  • --tls.yellow.min-decel FLOAT — minimum deceleration when braking at yellow 🟡
  • --railsignal-moving-block — let railsignals operate in moving-block mode by default
  • --railsignal.moving-block.default-classes STR[] — list of vehicle classes that default to moving-block operations
  • --railsignal.moving-block.max-dist FLOAT — max signal distance above which zipper conflicts get ignored
  • --railsignal.max-block-length FLOAT — don't build blocks longer than FLOAT, issue a warning instead ⚠️
  • --railsignal.default-classes STR[] — list of vehicle classes that use block-based insertion checks even when the network has no rail signals for them
  • --time-to-impatience TIME — how long a vehicle may wait before its impatience grows from 0 to 1. defaults to 300, and non-positive values disable impatience growth 😤
  • --default.departspeed STR — pick the default depart speed
  • --default.departlane STR — pick the default depart lane
  • --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 you don't specify it, the simulation step-length is used per default. vehicle- or VType-specific settings override the default. and it must be a multiple of the simulation step-length, no exceptions ✋
  • --default.carfollowmodel STR — pick the default car following model (Krauss, IDM, ...) 🚗
  • --default.speeddev FLOAT — pick the default speed deviation. a negative value implies vClass-specific defaults (0.1 for the default passenger class)
  • --default.emergencydecel STR — pick the 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
  • --overhead-wire.solver — use Kirchhoff's laws to solve the overhead wire circuit ⚡
  • --overhead-wire.recuperation — enable recuperation from the vehicle equipped with an elecHybrid device back into the overhead wire 🔋
  • --overhead-wire.substation-current-limits — enable current limits of the traction substation while solving the overhead wire electrical circuit ⚡
  • --emergencydecel.warning-threshold FLOAT — sets the fraction of emergency decel capability that has to be used to trigger a warning 🚨
  • --parking.maneuver — does parking simulation include maneuvering time and the associated lane blocking? 🅿️
  • --use-stop-ended — override stop until times with stop ended times when they're given
  • --use-stop-started — override stop arrival times with stop started times when they're given
  • --pedestrian.model STR — pick your pedestrian model among ['nonInteracting', 'striping', 'jupedsim', 'remote'] 🚶‍♀️
  • --pedestrian.timegap-crossing FLOAT — minimal acceptable gap, in seconds, between two vehicles before a pedestrian starts to cross
  • --pedestrian.striping.stripe-width FLOAT — width of the parallel stripes used to segment a sidewalk, in meters, for use with model 'striping' 🌈
  • --pedestrian.striping.dawdling FLOAT — factor for random slow-downs [0,1], for use with model 'striping' 🐢
  • --pedestrian.striping.mingap-to-vehicle FLOAT — minimal gap / safety buffer, in meters, from a pedestrian to another vehicle, for use with model 'striping'
  • --pedestrian.striping.jamtime TIME — time in seconds after which pedestrians start squeezing through a jam when using model 'striping' (non-positive values disable squeezing) 🫠
  • --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)
  • --pedestrian.striping.jamtime.narrow TIME — time in seconds after which pedestrians start squeezing through a jam while on a narrow lane, when using model 'striping'
  • --pedestrian.striping.jamfactor FLOAT — factor for reducing the speed of a pedestrian in a jammed state
  • --pedestrian.striping.reserve-oncoming FLOAT — fraction of stripes to reserve for oncoming pedestrians 🤝
  • --pedestrian.striping.reserve-oncoming.junctions FLOAT — how much of the stripes to set aside for pedestrians coming the other way, on crossings and walkingareas 💖 like it's giving generosity but make it math.
  • --pedestrian.striping.reserve-oncoming.max FLOAT — the max width, in m, you're allowed to reserve for those oncoming pedestrians 🎀
  • --pedestrian.striping.legacy-departposlat — interpret departPosLat for walks the legacy way, bestie. old-school vibes only 🦋
  • --pedestrian.striping.walkingarea-detail INT — generate INT intermediate points so the lanes inside the walkingarea get smoothed out ✨
  • --ride.stop-tolerance FLOAT — the tolerance applied when matching pedestrian and vehicle positions for boarding at individual stops 🚏
  • --mapmatch.distance FLOAT — the maximum distance allowed when mapping input coordinates (fromXY etc.) onto the road network 🗺️
  • --mapmatch.junctions — match positions to junctions instead of edges, periodt.
  • --mapmatch.taz — match positions to taz instead of edges 🎀
  • --weights.turnaround-penalty FLOAT — slap this time penalty on when computing routing costs for turnaround internal lanes 💅
  • --weights.reversal-penalty FLOAT — same energy but for train reversal. and heads up: negative values disable reversal 😭
  • --persontrip.walk-opposite-factor FLOAT — use FLOAT as a factor on walking speed when you're walking against the direction of vehicle traffic 🚶♀️

🧭 Routing Options 🧭

  • --routing-algorithm STR — pick your fighter from ['dijkstra', 'astar', 'CH', 'CHWrapper'] 👑
  • --weights.random-factor FLOAT — edge weights for routing get dynamically disturbed by a random factor drawn uniformly from [1,FLOAT) 🎲 chaos but make it deliberate.
  • --weights.random-factor.dynamic — when you're using --weights.random-factor, this varies the randomness over time. it's giving evolving chaos ⏳
  • --weights.minor-penalty FLOAT — apply this time penalty when computing minimum routing costs for minor-link internal lanes 🌸
  • --weights.tls-penalty FLOAT — apply scaled travel time penalties based on green split when computing minimum routing costs for internal lanes at traffic lights 🚦
  • --weights.priority-factor FLOAT — take edge priorities into account alongside travel times, weighted by this factor 🥇
  • --weights.separate-turns FLOAT — distinguish travel time by turn direction, and shift a fraction of the estimated time loss ahead of the intersection onto the internal edges 🔄
  • --astar.all-distances FILE — initialize the lookup table for astar from this file (generated by marouter --all-pairs-output) 📂
  • --astar.landmark-distances FILE — initialize the lookup table for the astar ALT-variant from this file 🗂️
  • --persontrip.walkfactor FLOAT — use FLOAT as a factor on pedestrian maximum speed during intermodal routing 🚶
  • --persontrip.transfer.car-walk STR[] — where mode changes from car to walking are allowed. possible values: 'parkingAreas', 'ptStops', 'allJunctions' and combinations 🚗➡️🚶
  • --persontrip.transfer.taxi-walk STR[] — where taxis can drop off customers ('allJunctions, 'ptStops', 'parkingAreas') 🚕
  • --persontrip.transfer.walk-taxi STR[] — where taxis can pick up customers ('allJunctions, 'ptStops', 'parkingAreas') 🙋♀️
  • --persontrip.default.group STR — when set, trips between the same origin and destination will share a taxi by default. carpooling era fr fr 🫶
  • --persontrip.taxi.waiting-time TIME — estimated time for taxi pickup ⏱️
  • --persontrip.ride-public-line — only use the intended public transport line, instead of any alternative line that stops at the destination 🚌 no side quests.
  • --railway.max-train-length FLOAT — use FLOAT as the maximum train length when initializing the railway router 🚂
  • --replay-rerouting — replay the exact rerouting sequence from vehroute-output 🔁
  • --device.rerouting.probability FLOAT — the probability that a vehicle has a 'rerouting' device 🎰
  • --device.rerouting.explicit STR[] — assign a 'rerouting' device to named vehicles, by name, no guessing 💌
  • --device.rerouting.deterministic — the 'rerouting' devices are set deterministic using a fraction of 1000 🎯
  • --device.rerouting.period TIME — the period with which the vehicle shall be rerouted ⏳
  • --device.rerouting.pre-period TIME — the rerouting period before depart 🕰️
  • --device.rerouting.adaptation-weight FLOAT — the weight of prior edge weights for exponential moving average ⚖️
  • --device.rerouting.adaptation-steps INT — the number of steps for the moving average weight of prior edge weights 👣
  • --device.rerouting.adaptation-interval TIME — the interval for updating the edge weights 🔄
  • --device.rerouting.threshold.factor FLOAT — only reroute if the new route is faster than the current route by the given factor 💨
  • --device.rerouting.threshold.constant TIME — only reroute if the new route is faster than the current route by the given TIME ⏱️
  • --device.rerouting.with-taz — use zones (districts) as routing startand endpoints 🗺️
  • --device.rerouting.mode STR — set routing flags (8 ignores temporary blockages) 🚧
  • --device.rerouting.init-with-loaded-weights — use weight files given with option --weight-files for initializing edge weights 📥
  • --device.rerouting.threads INT — the number of parallel execution threads used for rerouting 🧵 parallel bestie era.
  • --device.rerouting.synchronize — let rerouting happen at the same time for all vehicles 🕐 everyone on beat.
  • --device.rerouting.railsignal — allow rerouting triggered by rail signals 🚦🛤️
  • --device.rerouting.bike-speeds — compute separate average speeds for bicycles 🚲
  • --device.rerouting.output FILE — save adapting weights to FILE 💾
  • --person-device.rerouting.probability FLOAT — the probability that a person has a 'rerouting' device 🎲
  • --person-device.rerouting.explicit STR[] — assign a 'rerouting' device to named persons 💌
  • --person-device.rerouting.deterministic — the 'rerouting' devices are set deterministic using a fraction of 1000 🎯
  • --person-device.rerouting.period TIME — the period with which the person shall be rerouted ⏳
  • --person-device.rerouting.mode STR — set routing flags (8 ignores temporary blockages) 🚧
  • --person-device.rerouting.scope STR — which part of the person plan is to be replaced: stage, sequence, or trip 🔀

📋 Report Options 📋

  • -v, --verbose — switches to verbose output. she's chatty now 🗣️
  • --print-options — prints option values before processing 🖨️
  • -?, --help — prints this screen, or selected topics ❓
  • -V, --version — prints the current version 🏷️
  • -X, --xml-validation STR — set the schema validation scheme of XML inputs ("never", "local", "auto" or "always") ✅
  • --xml-validation.net STR — set the schema validation scheme of SUMO network inputs ("never", "local", "auto" or "always") 🌐
  • --xml-validation.routes STR — set the schema validation scheme of SUMO route inputs ("never", "local", "auto" or "always") 🛣️
  • -W, --no-warnings — disables output of warnings 🔇
  • --aggregate-warnings INT — aggregate warnings of the same type whenever more than INT occur 🧺 bundling the drama.
  • -l, --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 🚨
  • --log.timestamps — writes timestamps in front of all messages ⏰
  • --log.processid — writes process ID in front of all messages 🆔
  • --language STR — language to use in messages 🌍
  • --duration-log.disable — disable performance reports for individual simulation steps 🙅♀️
  • -t, --duration-log.statistics — enable statistics on vehicle trips 📊
  • --no-step-log — disable console output of the current simulation step 🤫
  • --step-log.period INT — number of simulation steps between step-log outputs 🪜

🌱 Emissions Options 🌱

  • --emissions.volumetric-fuel — return fuel consumption values in the (legacy) unit l instead of mg ⛽
  • --phemlight-path FILE — determines where to load PHEMlight definitions from 📁
  • --phemlight-year INT — enable fleet age modelling with the given reference year in PHEMlight5 📅
  • --phemlight-temperature FLOAT — set ambient temperature to correct NOx emissions in PHEMlight5 🌡️
  • --device.emissions.probability FLOAT — the probability that a vehicle has an 'emissions' device 🎲
  • --device.emissions.explicit STR[] — assign an 'emissions' device to named vehicles 💌
  • --device.emissions.deterministic — the 'emissions' devices are set deterministic using a fraction of 1000 🎯
  • --device.emissions.begin STR — recording begin time for emission-data ⏰
  • --device.emissions.period STR — recording period for emission-output 🔁

📡 Communication Options 📡

  • --device.btreceiver.probability FLOAT — the probability that a vehicle has a 'btreceiver' device 🎲
  • --device.btreceiver.explicit STR[] — assign a 'btreceiver' device to named vehicles 💌
  • --device.btreceiver.deterministic — the 'btreceiver' devices are set deterministic using a fraction of 1000 🎯
  • --device.btreceiver.range FLOAT — the range of the bt receiver 📶
  • --device.btreceiver.all-recognitions — whether all recognition point shall be written 📝
  • --device.btreceiver.offtime FLOAT — the offtime used for calculating detection probability (in seconds) ⏱️
  • --device.btsender.probability FLOAT — the probability that a vehicle has a 'btsender' device 🎲
  • --device.btsender.explicit STR[] — assign a 'btsender' device to named vehicles 💌
  • --device.btsender.deterministic — the 'btsender' devices are set deterministic using a fraction of 1000 🎯
  • --person-device.btsender.probability FLOAT — the probability that a person has a 'btsender' device 🎲
  • --person-device.btsender.explicit STR[] — assign a 'btsender' device to named persons 💌
  • --person-device.btsender.deterministic — the 'btsender' devices are set deterministic using a fraction of 1000 🎯
  • --person-device.btreceiver.probability FLOAT — the probability that a person has a 'btreceiver' device 🎲
  • --person-device.btreceiver.explicit STR[] — assign a 'btreceiver' device to named persons 💌
  • --person-device.btreceiver.deterministic — the 'btreceiver' devices are set deterministic using a fraction of 1000 🎯

🔋 Battery Options 🔋

  • --device.stationfinder.probability FLOAT — the probability that a vehicle has a 'stationfinder' device 🔌
  • --device.stationfinder.explicit STR[] — bestie, this one assigns a stationfinder device to named vehicles. like, you pick the names, it gets a stationfinder. 💅
  • --device.stationfinder.deterministic — the stationfinder devices are set deterministic using a fraction of 1000. no cap, that's the whole vibe. ✨
  • --device.stationfinder.rescueTime TIME — time to wait for a rescue vehicle on the road side when the battery is empty. literally the roadside rescue clock. 😭
  • --device.stationfinder.rescueAction STR — how to deal with a vehicle which has to stop due to low battery: [none, remove, tow]. pick your fighter. 💀
  • --device.stationfinder.reserveFactor FLOAT — scale battery need with this factor to account for unexpected traffic situations. it's giving cautious queen energy. 🎀
  • --device.stationfinder.emptyThreshold FLOAT — battery percentage to go into rescue mode. when it hits this, drama starts. 🚨
  • --device.stationfinder.radius TIME — search radius in travel time seconds. so not meters, bestie, seconds. ⏳
  • --device.stationfinder.maxEuclideanDistance FLOAT — Euclidean search distance in meters. a negative value disables the restriction. so if you're like nope, just go negative. 💅
  • --device.stationfinder.repeat TIME — when to trigger a new search if no station has been found. like a little retry timer. 🔁
  • --device.stationfinder.maxChargePower FLOAT — the maximum charging speed of the vehicle battery. zoom zoom but for electrons. ⚡
  • --device.stationfinder.chargeType STR — type of energy transfer. that's it, that's the tea. 🍵
  • --device.stationfinder.waitForCharge TIME — after this waiting time vehicle searches for a new station when the initial one is blocked. so if the first charger is taken, wait this long then go find another. 🫶
  • --device.stationfinder.minOpportunityDuration TIME — only stops with a predicted duration of at least the given threshold are considered for opportunistic charging. if your stop is too short, no charge for you. ⏱️
  • --device.stationfinder.saturatedChargeLevel FLOAT — target state of charge after which the vehicle stops charging. it's full, bestie, we can stop. 🔋
  • --device.stationfinder.needToChargeLevel FLOAT — state of charge the vehicle begins searching for charging stations. the panic threshold, basically. 😰
  • --device.stationfinder.opportunisticChargeLevel FLOAT — state of charge below which the vehicle may look for charging opportunities along its planned stops. lowkey opportunistic but in a cute way. ✨
  • --device.stationfinder.replacePlannedStop FLOAT — share of stopping time of the next independently planned stop to use for charging instead. so you're stealing a bit of the stop for electrons. 💅
  • --device.stationfinder.maxDistanceToReplacedStop FLOAT — maximum distance in meters from the original stop to be replaced by the charging stop. don't stray too far, babe. 📍
  • --device.stationfinder.chargingStrategy STR — set a charging strategy to alter time and charging load from the set: [none, balanced, latest]. pick your strategy, no cap. 🎯
  • --device.stationfinder.checkEnergyForRoute — only search for charging stations if the battery charge is not estimated sufficient to complete the current route. so if you're fine, don't even look. periodt. 💅
  • --device.battery.probability FLOAT — the probability for a vehicle to have a battery device. rng decides if you get one. 🎲
  • --device.battery.explicit STR[] — assign a battery device to named vehicles. you name them, they get battery. 🏷️
  • --device.battery.deterministic — the battery devices are set deterministic using a fraction of 1000. same deterministic energy. ✨
  • --device.battery.track-fuel — track fuel consumption for non-electric vehicles. yes, gas cars get tracked too. ⛽

🎀 Example Device Options 🎀

  • --device.example.probability FLOAT — the probability for a vehicle to have a example device. yes, example, literally. 🙈
  • --device.example.explicit STR[] — assign a example device to named vehicles. bestie, the grammar is not the point. 💅
  • --device.example.deterministic — the example devices are set deterministic using a fraction of 1000. iconic. 🎀
  • --device.example.parameter FLOAT — an exemplary parameter which can be used by all instances of the example device. a little parameter for the girlies. ⭐

🛰️ SSM Device Options 🛰️

  • --device.ssm.probability FLOAT — the probability for a vehicle to have a ssm device. rng but make it safety. 🎲
  • --device.ssm.explicit STR[] — assign a ssm device to named vehicles. named and monitored. 🏷️
  • --device.ssm.deterministic — the ssm devices are set deterministic using a fraction of 1000. deterministic safety slay. ✨
  • --device.ssm.measures STR — specifies which measures will be logged (as a space or comma-separated sequence of IDs in ('TTC', 'DRAC', 'PET', 'PPET', 'MDRAC')). pick your faves. 📊
  • --device.ssm.thresholds STR — specifies space or comma-separated thresholds corresponding to the specified measures (see documentation and watch the order!). only events exceeding the thresholds will be logged. bestie, the order MATTERS. 👀
  • --device.ssm.trajectories — specifies whether trajectories will be logged (if false, only the extremal values and times are reported). so false = just the highlights. ✨
  • --device.ssm.range FLOAT — specifies the detection range in meters. for vehicles below this distance from the equipped vehicle, SSM values are traced. it's giving personal space but with sensors. 📡
  • --device.ssm.extratime FLOAT — specifies the time in seconds to be logged after a conflict is over. required >0 if PET is to be calculated for crossing conflicts. so if you want PET for crossing, make it >0. no exceptions. ⚠️
  • --device.ssm.mdrac.prt FLOAT — specifies the perception reaction time for MDRAC computation. the prt, the moment. 💅
  • --device.ssm.file STR — give a global default filename for the SSM output. name the file, bestie. 📁
  • --device.ssm.geo — whether to use coordinates of the original reference system in output. original flavor, yes or no. 🌍
  • --device.ssm.write-positions — whether to write positions (coordinates) for each timestep. every step gets a lil location drop. 📍
  • --device.ssm.write-lane-positions — whether to write lanes and their positions for each timestep. lanes too, because why not. 🛣️
  • --device.ssm.write-na — whether to write conflict outputs with no data as NA values or skip it. NA or ghost? 👻
  • --device.ssm.exclude-conflict-types STR — which conflicts will be excluded from the log according to the conflict type they have been classified (combination of values in ('ego', 'foe' , '', any numerical valid conflict type code)). an empty value will log all and 'ego'/'foe' refer to a certain conflict type subset. complicated? yes. iconic? also yes. 💅

🚗 ToC Device Options 🚗

  • --device.toc.probability FLOAT — the probability for a vehicle to have a toc device. rng but for takeover. 🎲
  • --device.toc.explicit STR[] — assign a toc device to named vehicles. be specific, bestie. 🏷️
  • --device.toc.deterministic — the toc devices are set deterministic using a fraction of 1000. deterministic takeover era. ✨
  • --device.toc.manualType STR — vehicle type for manual driving regime. hands on the wheel energy. 🚗
  • --device.toc.automatedType STR — vehicle type for automated driving regime. hands off, but make it safe. 🤖
  • --device.toc.responseTime FLOAT — average response time needed by a driver to take back control. how long until they're like omg wait. 😭
  • --device.toc.recoveryRate FLOAT — recovery rate for the driver's awareness after a ToC. healing era. 🫶
  • --device.toc.lcAbstinence FLOAT — attention level below which a driver restrains from performing lane changes (value in [0,1]). if attention is low, no lane changes for you. 🚫
  • --device.toc.initialAwareness FLOAT — average awareness a driver has initially after a ToC (value in [0,1]). starting awareness, no cap. 🧠
  • --device.toc.mrmDecel FLOAT — deceleration rate applied during a 'minimum risk maneuver'. the safe stop slay. 🛑
  • --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. so 0 = no dynamic ToC, periodt. ⏱️
  • --device.toc.dynamicMRMProbability FLOAT — probability that a dynamically triggered TOR is not answered in time. TOR said, driver said nothing. 💀
  • --device.toc.mrmKeepRight — if true, the vehicle tries to change to the right during an MRM. right girlie behavior. ➡️
  • --device.toc.mrmSafeSpot STR — if set, the vehicle tries to reach the given named stopping place during an MRM. safe spot, we love to see it. 📍
  • --device.toc.mrmSafeSpotDuration FLOAT — duration the vehicle stays at the safe spot after an MRM. how long we chill. ⏳
  • --device.toc.maxPreparationAccel FLOAT — maximal acceleration that may be applied during the ToC preparation phase. prep phase zoom but capped. 🏎️
  • --device.toc.ogNewTimeHeadway FLOAT — timegap for ToC preparation phase. gap but in time. ⏲️
  • --device.toc.ogNewSpaceHeadway FLOAT — additional spacing for ToC preparation phase. extra room, bestie. 📏
  • --device.toc.ogMaxDecel FLOAT — maximal deceleration applied for establishing increased gap in ToC preparation phase. slow down to make space. 🐢
  • --device.toc.ogChangeRate FLOAT — rate of adaptation towards the increased headway during ToC preparation. how fast you ease into the new gap. 🌊
  • --device.toc.useColorScheme — whether a coloring scheme shall by applied to indicate the different ToC stages. pretty colors for stages. 🌈
  • --device.toc.file STR — switches on output by specifying an output filename. give it a file and it's logging. 📝

🧠 Driver State Device Options 🧠

  • --device.driverstate.probability FLOAT — the probability for a vehicle to have a driverstate device. rng decides if driver gets a state. 🎲
  • --device.driverstate.explicit STR[] — assign a driverstate device to named vehicles. name them and they get the state. 🏷️
  • --device.driverstate.deterministic — the driverstate devices are set deterministic using a fraction of 1000. deterministic driver state, slay. ✨
  • --device.driverstate.initialAwareness FLOAT — initial value assigned to the driver's awareness. starting awareness, bestie. 🧠
  • --device.driverstate.errorTimeScaleCoefficient FLOAT — time scale for the error process. errors but make it timed. ⏳
  • --device.driverstate.errorNoiseIntensityCoefficient FLOAT — noise intensity driving the error process. the chaos dial. 🔊
  • --device.driverstate.speedDifferenceErrorCoefficient FLOAT — general scaling coefficient for applying the error to the perceived speed difference (error also scales with distance). speed diff error, but distance matters too. 📏
  • --device.driverstate.headwayErrorCoefficient FLOAT — general scaling coefficient for applying the error to the perceived distance (error also scales with distance). distance perception? error. 📐
  • --device.driverstate.freeSpeedErrorCoefficient FLOAT — general scaling coefficient for applying the error to the vehicle's own speed when driving without a leader (error also scales with own speed). no leader, own speed error. 🛣️
  • --device.driverstate.speedDifferenceChangePerceptionThreshold FLOAT — base threshold for recognizing changes in the speed difference (threshold also scales with distance). when you notice speed diff changed. 👀
  • --device.driverstate.headwayChangePerceptionThreshold FLOAT — base threshold for recognizing changes in the headway (threshold also scales with distance). when you notice the gap changed. 👀
  • --device.driverstate.minAwareness FLOAT — minimal admissible value for the driver's awareness. don't go below this. 🚨
  • --device.driverstate.maximalReactionTime FLOAT — maximal reaction time (~action step length) induced by decreased awareness level (reached for awareness=minAwareness). slow reaction at min awareness. 🐢

🚨 Bluelight Device Options 🚨

  • --device.bluelight.probability FLOAT — the probability for a vehicle to have a bluelight device. emergency rng. 🚨
  • --device.bluelight.explicit STR[] — assign a bluelight device to named vehicles. named, lit, and loud. 💙
  • --device.bluelight.deterministic — the bluelight devices are set deterministic using a fraction of 1000. deterministic sirens, iconic. ✨
  • --device.bluelight.reactiondist FLOAT — set the distance at which other drivers react to the blue light and siren sound. they react when they're this close. 👮
  • --device.bluelight.mingapfactor FLOAT — reduce the minGap for reacting vehicles by the given factor. smaller gap when reacting, yes bestie. 📏

✨ FCD Device Options ✨

so your cars can spill out their whole little journey diary 📓

  • --device.fcd.probability FLOAT — the odds that a vehicle gets blessed with a 'fcd' device
  • --device.fcd.explicit STR[] — hand-pick which named vehicles get a 'fcd' device, no randomness
  • --device.fcd.deterministic — the 'fcd' devices are set deterministic using a fraction of 1000
  • --device.fcd.begin STR — the recording begin time for FCD-data ⏰
  • --device.fcd.period STR — the recording period for FCD-data
  • --device.fcd.radius FLOAT — record objects in a radius around equipped vehicles, so the fcd girlies can see their neighbors too

and the person-flavored ones, because pedestrians deserve lore too 🚶‍♀️

  • --person-device.fcd.probability FLOAT — the odds that a person gets a 'fcd' device
  • --person-device.fcd.explicit STR[] — assign a 'fcd' device to named persons
  • --person-device.fcd.deterministic — the 'fcd' devices are set deterministic using a fraction of 1000
  • --person-device.fcd.period STR — the recording period for FCD-data

✨ ElecHybrid Device Options ✨

electric girlies, this one's for you 🔋

  • --device.elechybrid.probability FLOAT — the odds that a vehicle gets the 'elechybrid' device
  • --device.elechybrid.explicit STR[] — assign a 'elechybrid' device to named vehicles
  • --device.elechybrid.deterministic — the 'elechybrid' devices are set deterministic using a fraction of 1000

✨ Taxi Device Options ✨

vroom vroom, someone call an Uber 💅

  • --device.taxi.probability FLOAT — the odds that a vehicle gets a 'taxi' device
  • --device.taxi.explicit STR[] — assign a 'taxi' device to named vehicles
  • --device.taxi.deterministic — the 'taxi' devices are set deterministic using a fraction of 1000
  • --device.taxi.dispatch-algorithm STR — the dispatch algorithm. pick your fighter: [greedy|greedyClosest|greedyShared|routeExtension|traci]
  • --device.taxi.dispatch-algorithm.output FILE — write information from the dispatch algorithm to FILE
  • --device.taxi.dispatch-algorithm.params STR — load dispatch algorithm parameters in format KEY1:VALUE1[,KEY2:VALUE]
  • --device.taxi.dispatch-period TIME — the period between successive calls to the dispatcher
  • --device.taxi.dispatch-keep-unreachable TIME — how long before we give up on unreachable reservations 😭
  • --device.taxi.idle-algorithm STR — what the idle taxis do with their free time [stop|randomCircling|taxistand]
  • --device.taxi.idle-algorithm.output FILE — write information from the idling algorithm to FILE
  • --device.taxi.vclasses STR[] — the network permissions that can be accessed by taxis

✨ GLOSA Device Options ✨

green light speed advisory, the ultimate "hurry up bestie" energy 🚦

  • --device.glosa.probability FLOAT — the odds that a vehicle gets a 'glosa' device
  • --device.glosa.explicit STR[] — assign a 'glosa' device to named vehicles
  • --device.glosa.deterministic — the 'glosa' devices are set deterministic using a fraction of 1000
  • --device.glosa.range FLOAT — the communication range to the traffic light
  • --device.glosa.max-speedfactor FLOAT — the maximum speed factor when approaching a green light 🟢
  • --device.glosa.min-speed FLOAT — minimum speed when coasting towards a red light 🔴
  • --device.glosa.add-switchtime FLOAT — extra time the vehicle is assumed to need to reach the intersection after the signal turns green
  • --device.glosa.use-queue — use the queue in front of the tls for GLOSA calculation
  • --device.glosa.override-safety — override safety features: ignore the current light state and always follow GLOSA's predicted state. yeah that's a spicy one, be careful 🌶️
  • --device.glosa.ignore-cfmodel — vehicles follow a perfect speed calculation: ignore speed calculations from the CF model if not safety critical

✨ Tripinfo Device Options ✨

receipts for the whole trip, we love documentation 🧾

  • --device.tripinfo.probability FLOAT — the odds that a vehicle gets a 'tripinfo' device
  • --device.tripinfo.explicit STR[] — assign a 'tripinfo' device to named vehicles
  • --device.tripinfo.deterministic — the 'tripinfo' devices are set deterministic using a fraction of 1000

✨ Vehroutes Device Options ✨

the itinerary stays on the record, periodt 🗺️

  • --device.vehroute.probability FLOAT — the odds that a vehicle gets a 'vehroute' device
  • --device.vehroute.explicit STR[] — assign a 'vehroute' device to named vehicles
  • --device.vehroute.deterministic — the 'vehroute' devices are set deterministic using a fraction of 1000

✨ Friction Device Options ✨

measurement chaos, but make it configurable 🫠

  • --device.friction.probability FLOAT — the odds that a vehicle gets a 'friction' device
  • --device.friction.explicit STR[] — assign a 'friction' device to named vehicles
  • --device.friction.deterministic — the 'friction' devices are set deterministic using a fraction of 1000
  • --device.friction.stdDev FLOAT — the measurement noise parameter which can be applied to the friction device
  • --device.friction.offset FLOAT — the measurement offset parameter which can be applied to the friction device → e.g. to force false measurements 👀

✨ FCD Replay Device Options ✨

for when you want to rewatch the tape 📼

  • --device.fcd-replay.probability FLOAT — the odds that a vehicle gets a 'fcd-replay' device
  • --device.fcd-replay.explicit STR[] — assign a 'fcd-replay' device to named vehicles
  • --device.fcd-replay.deterministic — the 'fcd-replay' devices are set deterministic using a fraction of 1000
  • --device.fcd-replay.file FILE — FCD file to read

✨ TraCI Server Options ✨

letting other programs pull up to the function 🤝

  • --remote-port INT — enables TraCI Server if set
  • --num-clients INT — the expected number of connecting clients

✨ Mesoscopic Options ✨

the zoomed-out, chill-lookin'-at-traffic-as-vibes mode 🦋

  • --mesosim — enables mesoscopic simulation
  • --meso-edgelength FLOAT — length of an edge segment in mesoscopic simulation
  • --meso-tauff TIME — factor for calculating the net free-free headway time
  • --meso-taufj TIME — factor for calculating the net free-jam headway time
  • --meso-taujf TIME — factor for calculating the jam-free headway time
  • --meso-taujj TIME — factor for calculating the jam-jam headway time
  • --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 (that's the default, btw)
  • --meso-multi-queue — enable multiple queues at edge ends
  • --meso-lane-queue — enable separate queues for every lane
  • --meso-ignore-lanes-by-vclass STR[] — do not build queues (or reduce capacity) for lanes allowing only the given vclasses
  • --meso-junction-control — enable mesoscopic traffic light and priority junction handling
  • --meso-junction-control.limited — enable mesoscopic traffic light and priority junction handling for saturated links. this prevents faulty traffic lights from hindering flow in low-traffic situations
  • --meso-tls-penalty FLOAT — apply scaled travel time penalties when driving across tls controlled junctions based on green split instead of checking actual phases
  • --meso-tls-flow-penalty FLOAT — apply scaled headway penalties when driving across tls controlled junctions based on green split instead of checking actual phases
  • --meso-minor-penalty TIME — apply a 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
  • --meso-overtaking — enable mesoscopic overtaking
  • --meso-recheck TIME — time interval for rechecking insertion into the next segment after failure
  • --meso-interpolate-pos — enable mesoscopic position interpolation

✨ Random Number Options ✨

the chaos engine, but you get to choose the chaos 🎲

  • --random — initialises the random number generator with the current system time
  • --seed INT — initialises the random number generator with the given value
  • --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)

✨ GUI Only Options ✨

the pretty-graphics era, we're so back 🎀

  • -g, --gui-settings-file FILE — load visualisation settings from FILE
  • -Q, --quit-on-end — quits the GUI when the simulation stops
  • -G, --game — start the GUI in gaming mode 🎮
  • --game.mode STR — select the game type ('tls', 'drt')
  • -S, --start — start the simulation after loading
  • -d, --delay FLOAT — use FLOAT in ms as delay between simulation steps
  • -B, --breakpoints STR[] — use TIME[] as times when the simulation should halt
  • -m, --edgedata-files FILE — load edge/lane weights for visualization from FILE
  • -N, --alternative-net-file FILE — load a secondary road network for abstract visualization from FILE
  • --selection-file FILE — load pre-selected elements from FILE
  • -D, --demo — restart the simulation after ending (demo mode)
  • -T, --disable-textures — do not load background pictures
  • --registry-viewport — load current viewport from registry
  • --window-size STR[] — create initial window with the given x,y size
  • --window-pos STR[] — create initial window at the given x,y position
  • --tracker-interval TIME — the aggregation period for value tracker windows
  • --osg-view — start with an OpenSceneGraph view instead of the regular 2D view
  • --gui-testing — enable overlay for screen recognition
  • --gui-testing-debug — enable output messages during GUI-Testing
  • --gui-testing.setting-output FILE — save gui settings in the given settings output file

🌈 EXAMPLES 🌈

living proof, here's how you actually run this thing:

sumo-gui -b 0 -e 1000 -n net.xml -r routes.xml

start a simulation from time 0 to 1000 with the given net and routes ✨

sumo-gui -c munich_config.cfg

start with a configuration file

sumo-gui --help

print help 🫶

🐛 REPORTING BUGS 🐛

okay bestie, if something's acting up, do not suffer in silence 💖 the maintainers literally want to hear about it. Bugs go here:

And if you wanna slide into their inbox instead, that's completely valid too:

  • <sumo@dlr.de>

Fr fr, that's the whole vibe — found a bug, tell the people, they'll be feral about fixing it. 🫶

✨ the receipts (aka build features, no cap) ✨

here's exactly what this build was cooked with, so when you file that issue you can copy-paste this and look super professional 😌💅:

Build features: Linux-6.8.0-139-generic x86_64 GNU 15.3.0 None
FMI Proj GUI Intl SWIG Eigen GDAL FFmpeg OSG GL2PS
Copyright (C) 2001-2026 German Aerospace Center (DLR) and others;
https://sumo.dlr.de

like, FMI, Proj, GUI, Intl, SWIG, Eigen, GDAL, FFmpeg, OSG, GL2PS… the whole squad showed up 🔥

Eclipse SUMO GUI 1.27.1 is part of SUMO. 🚗🌊

This program and the accompanying materials are made available under the terms of the Eclipse Public License v2.0 which accompanies this distribution, and is available at

This program may also be made available under the following Secondary Licenses when the conditions for such availability set forth in the Eclipse Public License 2.0 are satisfied: GNU General Public License, version 2 or later, which is available at

And the little license tag that says it all:

SPDX-License-Identifier: EPL-2.0 OR GPL-2.0-or-later
⚠️ no cap: you gotta actually respect these licenses. reading them is not optional, bestie. choose your license era ✨

💌 aaaand that's the whole page 💌

okay so this entire manual page right here? it's Eclipse SUMO GUI 1.27.1, dated August 2026, and it lives under the section ECLIPSE(1) — that's the source and version and date, all wrapped up like a little gift 🎀

ty for reading the whole thing, you absolute main character 👑 now go report that bug, run that sim, and eat something. i'm so proud of you, fr fr 💜🦋🌸

📦 where this page comes from