SUMO

Simulation of Urban MObility

User

Introduction
- The traffic simulation SUMO
Basic Usage
- Notation in this Documentation
- Needed, basic Computer Skills
- Installing SUMO
- Using SUMO Command Line Applications
- Tutorials
- Validating application inputs
Network Building
- SUMO Road Networks
- Abstract networks generation
- NETCONVERT
- Creating and modifying networks with NETEDIT
- Including elevation data
- Geo-Coordinates
Demand Modelling
- Introduction to SUMO Demand Modelling
- Definition of Vehicles, Vehicle Types, and Routes
- Simulation of public transport
- Simulation of individual persons and trip chains
- Simulation of logistics
- Shortest or Optimal Path Routing
- Intermodal Routing
- Routing in the Simulation
- Computing Dynamic User Assignment
- Generating pedestrian traffic demand
- Generate a vehicle type distribution to model the fleet
Data sources for demand generation
- Importing O/D Matrices
- - Other VISUM Demand Importers
  - Other Vissim Demand Importers
- Routes from Observation Points
- Routing by Turn Probabilities
- Activity-based Demand Generation
- Random Trips
Simulation
- Basic Definition
- Simulation output
- TraCI (On-line Interaction)
- Saving and Loading Simulation State
Traffic Management and Other Structures
- Traffic Lights
- Public Transport
- Variable Speed Signs
- Rerouter / Alternative Route Signage
- Vaporizer
- Dynamic calibration of flow and speed
- Parking areas
Traffic Modes
- Pedestrian simulation
- Bicycle simulation
- Railway simulation
- Waterway simulation
Additional Features
- Emissions
- Electric Vehicles
- Logistics
- Generic Parameters
- Shapes Visualisation
- Wireless Device Detection
- Emergency Vehicles
Model details
- Vehicle speed
- Vehicle insertion
- Vehicle permissions (access restrictions)
- Intersection dynamics
- Randomness
- Routing and Re-routing
- Sublane Model
- Opposite Direction Driving
- Safety
- Mesoscopic model
Common Problems
- Why Vehicles are teleporting
- Unexpected jamming
- Unexpected lane-changing maneuvers?
- How to get high flows?
Additional Tools
- osmWebWizard
- TraCI/Interfacing_TraCI_from_Python
- Reading SUMO networks and outputs with Python (sumolib)
- Tools for converting SUMO outputs to CSV/Spreadsheet
- Exporting mobility Traces (traceExporter)
- Determining the differences between two networks
- Tools/Visualization
- Tool index
Theory
- Traffic simulations in general
Application Manuals
- SUMO
- SUMO-GUI
- NETCONVERT
- NETEDIT
- NETGENERATE
- OD2TRIPS
- DUAROUTER
- JTRROUTER
- DFROUTER
- MAROUTER
- POLYCONVERT
- ACTIVITYGEN
- EMISSIONSMAP
- EMISSIONSDRIVINGCYCLE
Appendices
- ChangeLog
- Glossary
- FAQ
- Additional Tools
- Known File Extensions

Further Resources

Developer

Developer Docs
Daily Tests Status
Doxygen Documentation
Python Modules Documentation
- traci
- sumolib
Java Modules Documentation
- TraCI4J
- TraaS

Purgatory/NETCONVERT TlsComputation

generated on 2017-09-14 00:32:31.991356 from the wiki page for Purgatory/NETCONVERT_TlsComputation for SUMO 0.31.0

using always a pair is not proper in some cases; similar directions should be joined
left-movers are not computed properly (not recognized as such) for joined-TLSs
two incoming/two outgoing: what to do, here?
if only one major street is incoming, it is not used as such within the best match combination computation

This page was last modified on 6 September 2011, at 09:30.