Appendix B. Included Data

Appendix B. Included Data
Prev

Appendix B. Included Data

Table of Contents

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

B.1. Configuration File Templates

You can find the templates for each of the package's application's configuration files within the folder <SUMO_DIST>/data/cfg_templates. These templates may be filled with your own values. Examples of fille configuration files may be found within the examples-section.

B.2. Included Examples

Several examples are included in the distribution. You may find them in <SUMO_DIST>/data/examples. The subfolders have the following contents:

Table B.1. Supported example folders

Folder	Contains examples for (topic)	Contains examples for (application)
`dua`	the dynamic user assignment	SUMO/GUISIM, DUAROUTER
`duarouter`	building routes	DUAROUTER
`emissions`	vehicle emissions	SUMO/GUISIM
`extended`	additional simulation structures	SUMO/GUISIM
`jtrrouter`	building routes	JTRROUTER
`netbuild`	network generation	NETCONVERT, NETGEN
`output_tests`	simulation outputs	SUMO/GUISIM
`real_world`	networks from the real world	all
`simple_nets`	some simple scenarios	all
`traffic_lights`	traffic light algorithms	SUMO/GUISIM

B.2.1. SIMPLE_NETS: Basic Examples

Some smaller networks, mainly for testing purposes may be found within the <SUMO_DIST>/data/examples - folder. In respect to their shape, they are named "eight...", "cross..." and "box...". They differ in the number of lanes the edges have and whether a possibly existing junction is a simple right-of-way or a traffic light junction. The name pattern is as follows <SHAPE>Xl for networks with right-of-way junctions, where X is the number of lanes and <SHAPE>Xltl for networks with a traffic light. <SHAPE> is the name of the coarse shape of the network.

B.2.2. NETBUILD: Examples for NETCONVERT'S XML-Import

These examples may be found in the folder <SUMO_DIST>/data/examples/netbuilding. They shall show how networks may be imported/defined using the NETCONVERT application.

B.2.2.1. "types": Using Type Definitions to describe edges

Both of these two examples describe the same network (a simple cross), but "cross_notypes" describes each edge while "cross_usingtypes" uses types.

Location: <SUMO_DIST>/data/examples/netbuilding/types

B.2.2.2. "speed_in_kmh": Defining Edges' Speed Limits in km/h

Both of these two examples describe the same network (a simple cross) as the settings in <SUMO_DIST>/data/examples/netbuilding/types, but the speed is given in km/h, both within edge definitions (cross_notypes_kmh) and within the version using types (cross_usingtypes_kmh).

Location: <SUMO_DIST>/data/examples/netbuilding/speed_in_kmh

B.2.2.3. "shapes": Defining the Shapes of Edges

One can pass an additional parameter to edges to describe a more complex shape. This example is one for using this attribute.

Location: <SUMO_DIST>/data/examples/netbuilding/shapes/hokkaido-japan

B.2.3. ROUTER: Examples for DUAROUTER and JTRROUTER

These examples may be found in the folder <SUMO_DIST>/data/examples/router. They shall show how trips and flows may be used to define vehicles.

B.2.3.1. "trips2routes", "trips2routes_repetition", "flows2routes": Different Definition Types for the Same

All these three examples generate 100 vehicles which all have the same route. In "trips2routes" each vehicle has an own route. They all are the same, only the vehicles' ids differ. "trips2routes_repetition" generates one vehicle but which is duplicated within the simulation 100 times. "flows2routes" generates 100 vehicles and routes using a flow definition. The vehicles differ from those generated by "trips2routes" only by their ids.

Location: <SUMO_DIST>/data/examples/router

B.2.3.2. "flows2routes" vs. "flows2routes_`X`s_interval" vs. "flows2routes_`X`s_interval_ext": Spreading vehicles over an interval

These examples show the usage of the interval length in flows. While in "flows2routes" all vehicles are emitted at the same time, in "flows2routes_100s_interval" the departure times are spread over 100s and in "flows2routes_200s_interval" over 200s. The example ending with "_ext" show how the interval may be defined using an enclosing element.

Location: <SUMO_DIST>/data/examples/router

B.2.4. EXTENDED: Examples for using additional SUMO-structures

These examples may be found in the folder <SUMO_DIST>/data/examples/extended. They show how simulations may be equipped with additional structures such as variable speed signs, bus routes etc..

B.2.4.1. "busses1" vs. "3busses1": Examples for Bus Stops

"busses1" shows how bus stops are defined and a bus is forced to stop at these. "3busses1" is almost the same, but three busses are moving around. "3busses1" shows also that the length of bus stops determines how many busses may stop here.

Location: <SUMO_DIST>/data/examples/extended

B.2.4.2. "vehicle_stops": Defining Stop Positions for Vehicles

"vehicle_stops" shows how a vehicle can be forced to stop at a certain postion.

Location: <SUMO_DIST>/data/examples/extended

Prev
Appendix A. Naming Conventions	Home