SUMO - Simulation of Urban MObility - User Documentation
		Next

SUMO - Simulation of Urban MObility - User Documentation

Daniel Krajzewicz

Michael Behrisch

$Revision: 6595 $

Table of Contents

1. Introduction

1.1. What is SUMO?

1.2. Why open source?

1.3. Features

1.4. About this Document

1.4.1. Described Applications
1.4.2. Notation
1.4.3. Status

1.5. Call for Help

2. First Steps

2.1. Installing SUMO
2.2. Running the Examples

3. Traffic Simulations and SUMO

3.1. A short Introduction to Traffic Simulation Theory

3.1.1. Simulation types
3.1.2. Needed Data

3.2. The Workflow of Preparing a Simulation

3.3. SUMO

3.3.1. Main Software Paradigms

4. Network Generation

4.1. Introduction

4.2. Building Networks from own XML-descriptions

4.2.1. Nodes Descriptions
4.2.2. Edges Descriptions
4.2.3. Types Descriptions
4.2.4. Connection Descriptions
4.2.5. Building the Network

4.3. Converting other Input Data

4.3.1. Importing ArcView-databases
4.3.2. Importing VISSIM-networks
4.3.3. Importing VISUM-networks
4.3.4. Importing Elmar's converted NavTech-Files
4.3.5. Importing TIGER-databases

4.4. Further NETCONVERT Options

4.4.1. Setting default Values
4.4.2. Adding Turnarounds
4.4.3. Removing Geometry Nodes
4.4.4. Using Edges' maximum Speed Definitions in km/h
4.4.5. Importing Networks without Traffic Light Logics
4.4.6. Guessing On- and Off-Ramps
4.4.7. Converting from Geocoordinates
4.4.8. Inner-junction Traffic
4.4.9. Constraining the Input
4.4.10. Additional Output

4.5. Automatic Network Generation

4.5.1. Grid-like Networks
4.5.2. Spider-net-like Networks
4.5.3. Random Networks

4.6. Closing Thoughts (so far)

4.7. Recent Changes

4.8. Missing

5. Route Generation

5.1. Introduction

5.2. Common, mandatory Values

5.3. Building Routes from Scratch

5.3.1. Generating own, explicit Routes
5.3.2. Generating random Routes
5.3.3. Using the Junction Turning Ratio - Router
5.3.4. Using OD2TRIPS

5.4. Importing Routes from other Simulations

5.4.1. Importing VISSIM und VISUM-routes

5.5. Dynamic User Assignment and Alternative Routes

5.5.1. Automatic Iteration using 'dua-iterate.py'

5.6. Additional Weights

5.7. Using Detectors and DFROUTER

5.7.1. Computing Detector Types
5.7.2. Computing Routes
5.7.3. Computing Flows
5.7.4. Saving Flows and other Values

5.8. Closing Thoughts (so far)

5.9. Recent Changes

5.10. Missing

6. Performing the Simulation

6.1. Output Generation

6.1.1. Detectors
6.1.2. Network State Dump
6.1.3. Aggregated Lane/Edge States (Edge/Lane-Dumps)
6.1.4. Net-Wide Vehicle Emission States & Travel Times
6.1.5. Vehicle-Oriented Trip Information
6.1.6. Vehicle Routes
6.1.7. Output coupled to Traffic Lights

6.2. Vehicles Handling Revisited

6.2.1. Emitter

6.3. Traffic Management and Other Structures

6.3.1. Traffic Lights
6.3.2. Public Transport
6.3.3. Variable Speed Signs (VSS)
6.3.4. Rerouter
6.3.5. Vehicle Classes

6.4. Using the Files in a correct Way

6.5. Other Topics

6.5.1. Simulation of Accidents

6.6. Missing

7. Simulation-GUI

7.1. Main Window Interface

7.1.1. Menu Bar
7.1.2. Tool Bar

7.2. Simulation Window Interfaces

7.2.1. Common Controls

7.3. Interacting with Objects

7.3.1. Display an Object's Name
7.3.2. Object Popup Menus
7.3.3. Object Selection
7.3.4. Parameter Windows
7.3.5. TL-Tracker Windows

7.4. Additional Geometry Files

7.4.1. Polygon Definitions
7.4.2. Point-of-interest Definitions

8. Tips, Tricks and Tools

8.1. Using Configuration Files

8.2. Additional Meta-Information

8.3. Additional Tools

8.3.1. Polygon Conversion
8.3.2. Helpers for DUA-Computation
8.3.3. Handling Routes and Route Alternatives

A. Naming Conventions

B. Included Data

B.1. Configuration File Templates

B.2. Included Examples

B.2.1. SIMPLE_NETS: Basic Examples
B.2.2. NETBUILD: Examples for NETCONVERT'S XML-Import
B.2.3. ROUTER: Examples for DUAROUTER and JTRROUTER
B.2.4. EXTENDED: Examples for using additional SUMO-structures

List of Figures

3.1. The different simulation granularities; from left to right: macroscopic, microscopic, sub-microscopic (within the circle: mesoscopic)
3.2. The difference between a space-continuous (top) and a space-discrete (bottom) simulation
3.3. Process of simulation with SUMO; (rounded: definite data types; boxes: applications; octagons: abstract data types)
4.1. Building a network
4.2. Building a network from XML-descriptions
4.3. Coordinate system used in SUMO
4.4. Unconstrained Network (zoom=2200)
4.5. Network with explicit edge-2-edge connections
4.6. Network with explicit lane-2-lane connections
4.7. Network with explicite prohibitions
4.8. netgen --grid-net --grid-number=10 --grid-length=400 --output-file=MySUMOFile.net.xml
4.9. netgen --grid-net --grid-x-number=20 --grid-y-number=5 --grid-y-length=40 --grid-x-length=200 --output-file=MySUMOFile.net.xml
4.10. netgen --spider-net --spider-arm-number=10 --spider-circle-number=10 --spider-space-rad=100 --output-file=MySUMOFile.net.xml
4.11. netgen --spider-net --spider-arm-number=4 --spider-circle-number=3 --spider-space-rad=100 --output-file=MySUMOFile.net.xml
4.12. netgen --random-net -o MySUMOFile.net.xml --rand-iterations=200 --abs-rand
5.1. Building routes
5.2. A network where the usage of random routes causes an improper behaviour due to the mixture of rural and minor roads
5.3. Building trips from the OD-matrix
5.4. Example DUA-network (from "<SUMO_DIST>/data/examples/dua/dua3s*")
5.5. Sketch showing the effects of Christian Gawron dua-approach on route distribution within the network; blue color indicates that an edge is used within the step, red shows jams
6.1. Visualization of a bus stop in SUMO (from <SUMO_DIST>/data/examples/extended/busses1)
7.1. The GUI-Window with a loaded simulation (violet: names of the controls as used below)
7.2. A sample Parameter Window (for an induction loop in this case)
7.3. A sample Parameter Window (for the number of vehicles within a simulation in this case)
7.4. A sample usage of the aggregation option (for an induction loop in this case, for aggregation times of 1s, 1min, 5min (from left to right))
7.5. A sample usage of the tls-tracker

List of Tables

1.1. Applications described within this document
4.1. Entries read by NETCONVERT
4.2. Possible entries to override NavTech-information
4.3. Imported VISUM-tables
6.1. Definition of values generated by e1-detectors
6.2. Definition of values generated by e2-detectors
6.3. Definition of values generated by e3-detectors
6.4. Definition of values generated by e2-detectors
6.5. Definition of values generated by edgedump/lanedump-outputs
6.6. Definition of values generated by emissions-output
6.7. Definition of values generated by tripinfo-output
6.8. Allowed vehicle class authority descriptions
6.9. Allowed vehicle class vehicle kind descriptions
B.1. Supported example folders

		Next
		Chapter 1. Introduction