SUMO-GUI

generated on 2018-12-14 00:24:44.792642 from the wiki page for SUMO-GUI for SUMO git

From 30.000 feet

SUMO-GUI is basically the same application as SUMO, just extended by a graphical user interface.

Purpose: Simulates a defined scenario
System: portable (Linux/Windows is tested); opens a window
Input (mandatory): A SUMO-configuration file (see SUMO)
Output: SUMO-GUI generates the same output as SUMO
Programming Language: C++

Usage Description

Initial appearence of SUMO-GUI; may differ from what you see

Being a window-based application, SUMO-GUI is started by a double click with the left mouse button on Windows, on Linux probably with a single click. After this, an empty window should show up, similar to the one shown in the image.

Using either the "File->Open Simulation..." menu entry or by using the "open"-icon (Open sim.gif), you should be able to load an existing SUMO configuration file, if it has the proper extension ".sumocfg". If the SUMO configuration file is erroneous, the errors are reported, otherwise your network referenced within the configuration file should be shown. Now you can start to simulate by pressing the "play" button (Play.gif). The simulation works as if being started on the command line. The simulation can be halted using the "stop" button (Stop.gif) and continued by pressing the "play" button again. When stopped, also single steps may be performed by pressing the "single step" button (Step.gif).

If the simulation is running, the current simulation second is shown in the "digital digits" field, right to "Time:" (Current step example.gif). By clicking on the word "Time:", the display can be toggled between showing <seconds> and <hour:minute:seconds>.

Next to the time display is the delay control (Delay.png). This allows you to slow down the simulation by waiting for the given number of milliseconds between simulation steps.

Note:
By default the delay is set to 0. This can result in a simulation that runs too fast to see any vehicles. Increase the delay value if this happens.

Besides loading simulation configurations, it is also possible to load networks by using either the "File->Open Network..." menu entry or by using the "open network"-icon (Open net.gif). Please note, that normally SUMO-GUI assumes networks have the extension ".net.xml", but also accepts other extensions.

Both, the loaded simulation or the loaded network may be reloaded using the "reload" button (Reload.gif) or the menu entry "File->Reload".

If a network or a simulation are loaded, the navigation through the network is possible with the mouse or with the keyboard. One can drag the network with the left mouse button pressed into all directions and zoom either by using the mouse wheel or by pressing the right mouse button and moving the mouse up and down. For fine grained zooming (half zoom speed) press the "Control" key while using the mouse wheel, for double speed use "Shift".

Interaction with the View

Basic Navigation

The viewport editor

As soon as a network is displayed, one can interact with the view. Pressing the left mouse button within the view and moving the mouse with the button pressed, will shift the network. Moving the mouse up and down while pressing the right mouse button changes the zoom of the network. It is also possible to change the zoom by using the mouse wheel (holding <SHIFT> increases the zooming speed and holding <CTRL> lowers it). Zooming is either focused on the center of the screen or on the cursor position. The zoom style can be selected with the Zoomstyle.png button.

You can also control which part of the network is visible by directly setting the network coordinates which shall be at the center of the screen along with the zoom (given a value of 100 the whole network will fit onto the screen). These settings can be changed by opening the viewport editor using the Open viewport editor.gif button. From this editor, it is possible to save the current settings (Save.gif) or load previously saved ones (Open sim.gif within the viewport editor).

The viewport is defined as following: <viewport zoom="<ZOOM>" x="<X>" y="<Y>"/>. It can be loaded as a part of viewsettings.

Pressing the center-button (Center.gif) from the menu bar at the top of the view, will reset the viewport so that the complete network is shown.

Breakpoints

The simulation can be stopped automatically to allow investigating specific points in time. Breakpoints can be set via any of the following methods:

  • via menu Edit->Breakpoints
  • by setting option --breakpoints TIME1,TIME2,...
  • by loading #Configuration_Files with breakpoint information

Keyboard Shortcuts

Various menu items are accessible via keyboard shortcuts. These are documented directly in the menu. (i.e. Ctrl-l Ctrl-e opens the edge locator, Ctrl-d performs a single simulation step). Additional shortcuts are listed below:

  • Ctrl-LeftClick: toggle selection status of object under cursor
  • Arrow Keys: move the view
  • Ctrl + Arrow keys: move the view less
  • PageUp / PageDow: move the view up/down (a lot)
  • Shift + PageUp / PageDow: move the view left/right (a lot)
  • +/-, Keypad +/-: zoom in/out
  • Home/Keypad Home: recenter view
  • Ctrl + v: open view settings dialog

Object Properties / Right-Click-Functions

Right-clicking simulation objects gives access to additional information:

  • copy object id
  • object parameter dialog (menu item Show Parameter)
  • position information (x,y and lat,lon)
  • select/deselect object

The following objects can be accessed by right-click:

  • Vehicles (some attributes are only availabe when using a specific simulation model, i.e. MESO or sublane model)
  • Persons
  • Lanes
  • Junctions
  • Traffic Lights (by clicking on the green/red colored bars)
  • Detectors
  • Rerouters
  • Variable Speed Signs
  • POIs
  • Polygons
  • Simulation (by clicking the background where there is no other object). Also accessible by clicking the SimulationParameters.png button.
    Note:
    Simulation Parameters include all values available via verbose output such as departed, running and arrived vehicles. It also includes network statistics such as number of edges and nodes.

The following additional functions are available via right-click:

  • Tracking movements (vehicles and persons)
  • Activate additional visualizations (persons and vehicles)
  • Select junction foe vehicles (vehicles). Requires coloring vehicles by selection to be visible
  • Close for traffic (edges and lanes)
  • Switch programs (traffic lights)
  • Set speed limit (variable speed sign)

Selecting Objects

SUMO-GUI allows for the selection of arbitrary network elements such as edges, lanes and junctions, which can be saved to a file (and also loaded from a file) for further processing. Selection is done by either choosing "Add To Selected" from the context menu (right click) of the element or by clicking left on an element while pressing the "Control" key.

The selected elements can be saved / loaded and looked at in the "Edit Selected" dialog available from the edit menu. The list contains entries of the form objectType:objectId with each of these entries on a separate line:

edge:someEdge
edge:someOtherEdge
junction:myJunction

Most network objects can be colored according to their selection status (color by selection) and selected network elements may be manipulated as a group in NETEDIT.

Locating Objects

All simulation objects can be located based on their ID by using the locate dialog Locate.png. By clicking this button a sub-menu for selecting the object type is openend. The following types are available:

After selecting the object type, a dialog opens that provides a text box for entering the object ID. Search for objects starts after the first characters are entered until an object ID that starts with these characters is found. Once selected in the object list, the view can be centered on that object.

The button Hide unselected, restricts the object list to selected objects of that type. The Locate Menu in the main menu bar also contains a check-box that toggles whether internal edges and internal junctions shall be listed in the object locator dialog.

Influencing the simulation

Currently, there is only very little interaction that can be done from the GUI. This will change in the future (see below)

Switching Traffic Lights

By right-clicking on the colored bars at an intersection, a popup-menu allows switching between all signal plans that have been loaded. The special program off is always available and can be used to switch the intersection into a priority-intersection.

Closing and Opening Edges and Lanes

By right clicking on a lane, each lane (or the corresponding edge) can be closed for all traffic (except vClass authority and ignoring) by selecting the option Close lane or Close edge. In the same way lanes or edges can be reopened for traffic by selecting Reopen lane or Reopen edge.

Planned Interactions

In the future more interactions are planned for exploratory simulation:

  • changing simulation options dynamically (i.e. --scale, --time-to-teleport, ....
  • adding traffic
  • changing vehicle or vehicle type parameters
  • testing TraCI function calls

Understanding what you see

Right of way

At the end of every lane and at the outset of a junction there is a little colored bar which indicates right of way. When there are multiple target lanes from one lane, the bar is split in smaller parts each indication the rules for one connection. The colors a defined as follows:

  • FOO Traffic light, green phase, vehicle has right of way
  • FOO Traffic light, green phase, vehicle has to yield to some streams
  • FOO Traffic light, red phase, vehicle has to wait
  • FOO Traffic light, red/yellow phase, indicates upcoming green phase, vehicle has to wait
  • FOO Traffic light, yellow phase, vehicle should stop if possible
  • FOO Traffic light, off-blinking, vehicle has to yield
  • FOO Traffic light, off-no-signal, vehicle has right of way
  • FOO uncontrolled, vehicle has right of way
  • FOO uncontrolled, vehicle has to yield to some streams
  • FOO uncontrolled, right-before-left rules, all vehicles yield to the rightmost incoming lane
  • FOO uncontrolled, stop-sign / controlled, right-turn arrow, vehicle has to stop and then yield
  • FOO uncontrolled, allway-stop, all vehicles have to stop and then drive in the order of arrival
  • FOO uncontrolled, zipper, vehicles have to perform zipper merging
  • FOO dead-end, vehicle may not drive there
Note:

If a vehicle is braking in the simulation, the responsible foe vehicle (if any) can also be identified directly by taking the following steps:
- set vehicle coloring to color by selection
- right-click the braking vehicle and then click Select Foes

The foe vehicles will then be color with the selection color (typically blue).

Road Access Permissions

Road access permissions are an important tool for building multi-modal scenarios. To better understand the road network configuration there are various ways to support coloring according to permissions.

Default Coloring

The default coloring scheme (uniform) aims to color roads in a realistic way and also show some basic access permissions. The road colors have to following meaning:

  • FOO sidewalk (allow="pedestrian")
  • FOO bike lane (allow="bicycle")
  • FOO waterway (allow="ship")
  • FOO closed lane (allow="authority")
  • FOO green verge (disallow="all")
  • FOO anything else that does not allow passenger
  • FOO anything else

Color by permission code

Each possible set of access combinations is represented by a unique numerical code. The code for each lane can be retrieved from the lane parameter dialog (permission code). The lane coloring scheme permission code allows assigning an individual color for each of code. This can be used for arbitrary coloring according to the users needs (the default coloring scheme can be regarded as a special case of this coloring type).

Show permissions for a specific vehicle class

To investigate connectivity in the network, it is often useful to quickly highlight lanes that allow a specific vehicle class. This can be done from the main menu by selecting Edit->Select lanes which allow ...->the desired vehicle class.

This changes the current selection to the set of all lanes that allow the specified vehicle class and also changes the coloring scheme to color by selection. All lanes that allow the selected vehicle class will be shown in blue (by default).

Connectivity

At each intersection all incoming lanes that allow driving across the intersection have one or more white arrows to show the allowed driving directions. However, these arrows only give partial information since every lane may have more connections than the number of arrows. For example, when a lane targets two lanes one the same edge beyond the intersection, only one arrow will be drawn even though two distinct connections exist.

  • To see all connections, activate the junction visualization option Show lane to lane connections. The collors of the connection lines correspond to the #Right_of_way-colors.
  • Each connection at an intersection has a unique index starting at 0 and going clockwise around the intersection. These indices can be shown using the junction visualization option Show link junction index.
  • Each connection that is controlled by a traffic light has a unique index with regard to that traffic light. By default each traffic light controls one intersection and these indices are identical to the link junction index mentioned above. In the case of joined traffic lights which control multiple intersections, the indices are different. Also, the indices may be freely customized by the user (e.g. to define signal groups). These indices are shown using the junction visualization option Show link tls index.

Changing the appearance/visualisation of the simulation

The View Settings menu allows to change and customize the simulations' appearance and visualization. To open the visualization settings use Colorwheel.gif in the menu bar at the top of the view.

For customizing the simulation one can make changes e.g. to the background coloring, streets and vehicle appearance as well as the visualization of POIs. Furthermore one can save (Save to registry.gif) and delete (Delete from registry.gif‎) settings to the registry or export (Save.gif) custom made settings files and load previews settings again Open sim.gif. So one can use different favorite settings files for any simulation.

The current settings file is shown in a drop down menu in the top bar of the View Settings window where you can switch back to default settings.

Common Visualization Settings

Separate settings exist for different simulation objects such as vehicle, lanes, persons and detectors. Some options exist for all (or most) of these objects:

  • Size options
    • Exaggerate by: Draws objects bigger to make them more visible
    • Minimum Size: Do not draw objects below a minimum size
    • Draw with constant size when zoomed out: Automatically increase the drawing size when zooming out to keep the visual size constant.
  • Name options
    • Show name: Disable drawing of object IDs
    • Size: Size of the drawn ID (visual size will stay constant when zooming)
    • Color: Color of drawn ID
  • Coloring options: Color by some attribute and change the color value/range

Vehicle Visualisation Settings

Table 1.1 Vehicle shape schemes

Name Description
triangle All vehicles are shaped triangular
boxes All vehicles are shaped square
simple shapes All vehicles have simple car shape
raster images All vehicles are drawn with a loaded bitmap defined for their type using attribute imgFile (using simple shapes as fallback)


Table 1.2 Vehicle coloring schemes and boundaries

Name Measure Description
given vehicle/type/route color - The color given within the vehicle definition with fallback to type and then to route color
uniform - All vehicles are colored uniformly
given/assigned vehicle color - The color given within the vehicle definition
given/assigned type color - The color given within the vehicle type definition
given/assigned route color - The color given within the vehicle route definition
depart position as HSV - The depart position of each vehicle, relative to the network center, is used to color the vehicle. Direction will be used as H(ue), distance from the center as S(aturation), V(alue) is always 1.
arrival position as HSV - The arrival position of each vehicle, relative to the network center, is used to color the vehicle. Direction will be used as H(ue), distance from the center as S(aturation), V(alue) is always 1.
direction/distance as HSV - The direction and distance between a vehicle's departure and arrival position, are used to color the vehicle. Direction will be used as H(ue), distance from the center as S(aturation), V(alue) is always 1.
by speed m/s The current vehicle speed
by waiting time s The time for which a vehicle is halting
by accumulated waiting time s The total time for which a vehicle has been halting recently (default: within the last 300s.)
by time since last lanechange s The time since the last lane change. The color also indicates the direction of the last lane-change (negative values indicated a change to the right).
by max speed m/s Vehicle's maximum velocity
by CO2 emissions g/s The amount of CO2 currently emitted by the vehicle
by CO emissions g/s The amount of CO currently emitted by the vehicle
by PMx emissions g/s The amount of PMx currently emitted by the vehicle
by NOx emissions g/s The amount of NOx currently emitted by the vehicle
by HC emissions g/s The amount of HC currently emitted by the vehicle
by fuel consumption l/s The consumed fuel
by electricity consumption kWh/s The consumed electricity (for electric vehicles only)
by noise emissions dbA The noise produced by the vehicle
by reroute number count The number of times this vehicle has bee rerouted
by selection - Colors selected and unselected vehicles differently
by offset from best lane count By the number of immediate lane changes the vehicle must perform in order to follow its route
by accleration m/s^2
by time gap s By the time to collide with the leader vehicle assuming constant speeds


In addition to the vehicle shape and coloring one can display blinker and brake lights, the minimum gap, and the vehicle name. The vehicle names will always be scaled to the chosen size, no matter which zoom step is chosen.

Edge/Lane Visualisation Settings

Table 2.1 Lane coloring schemes

Name Measure Description
uniform - All road edges are drawn using the same color. Bicycle lanes are drawn in brown, sidewalks in grey and prohibited lanes (allowing no vehicle classes) are transparent.
by selection (lane-/streetwise) - selected lanes are drawn different than those that are not
by permission code - all lanes are colored according to the permitted vehicle classes. The code for each lane can be retrieved from the lane parameter dialog (permission code).
by allowed speed (lanewise) m/s The maximum velocity allowed on this lane
by current occupancy (lanewise, brutto)  % / 100 By the amount of place that is covered by vehicles (including minGap)
by current occupancy (lanewise, netto)  % / 100 By the amount of place that is covered by vehicles (excluding minGap)
by first vehicle waiting time (lanewise) s By the time the first vehicle on the lane waits
by lane number (streetwise) - By the number of lanes this edge has
by CO2 emissions g/s The mean amount of CO2 emitted per a lane's meter
by CO emissions g/s The mean amount of CO emitted per a lane's meter
by PMx emissions g/s The mean amount of PMx emitted per a lane's meter
by NOx emissions g/s The mean amount of NOx emitted per a lane's meter
by HC emissions g/s The mean amount of HC emitted per a lane's meter
by fuel consumption l/s The mean amount of consumed fuel per a lane's meter
by electricity consumption kWh/s The mean amount of consumed electricity per a lane's meter
by noise emission dBa The noise generated by the vehicles on the lane
by global travel time s The travel time on that edge loaded from a weight file
by global speed percentage  % By the fraction of the maximum speed that the edge allows based on travel times from a loaded weight file
by given length/geometrical length The factor by which the geometrical length differs from the user-specified edge length
by angle The angle of the edge measured from start to end (excluding in-between geometry)
by loaded weight By the value loaded using options --weight-files, --weight-attribute
by priority By the right-of-way priority using during network building
by height at start m By the z-coordinate at the start of the lane
by height at segment start m By the z-coordinate at the start of each geometry segment
by inclination  % By the average change in height between start and end of the lane per m
by segment inclination  % By the average change in height between start and end of each geometry segment
by average speed m/s By the average speed of vehicles on the lane
by average relative speed  % By the average speed of vehicles on the lane as percentage of the allowed speed

Table 2.2 Lane scaling schemes

Name Measure Description
by selection (lane-/streetwise) - selected lanes are drawn different than those that are not
by allowed speed (lanewise) m/s The maximum velocity allowed on this lane
by current occupancy (lanewise, brutto)  % / 100 By the amount of place that is covered by vehicles (including minGap)
by current occupancy (lanewise, netto)  % / 100 By the amount of place that is covered by vehicles (excluding minGap)
by first vehicle waiting time (lanewise) s By the time the first vehicle on the lane waits
by lane number (streetwise) - By the number of lanes this edge has
by CO2 emissions g/s The mean amount of CO2 emitted per a lane's meter
by CO emissions g/s The mean amount of CO emitted per a lane's meter
by PMx emissions g/s The mean amount of PMx emitted per a lane's meter
by NOx emissions g/s The mean amount of NOx emitted per a lane's meter
by HC emissions g/s The mean amount of HC emitted per a lane's meter
by fuel consumption l/s The mean amount of consumed fuel per a lane's meter
by electricity consumption kWh/s The mean amount of consumed electricity per a lane's meter
by noise emission dBa The noise generated by the vehicles on the lane
by global travel time s The travel time on that edge loaded from a weight file
by global speed percentage  % By the fraction of the maximum speed that the edge allows based on travel times from a loaded weight file
by given length/geometrical length The factor by which the geometrical length differs from the user-specified edge length
by angle The angle of the edge measured from start to end (excluding in-between geometry)
by loaded weight By the value loaded using options --weight-files, --weight-attribute
by priority By the right-of-way priority using during network building
by average speed m/s By the average speed of vehicles on the lane
by average relative speed  % By the average speed of vehicles on the lane as percentage of the allowed speed

In addition to the lane / edge coloring one can display lane borders, link decals, rails, edge names, street names, internal edge names, and hide macro connectors. The edge names as well as the street and internal edge names will always be scaled to the chosen size, no matter which zoom step is chosen.

Loading Shapes and POIs

Polygonal shapes and Points of Interests (POIs) can either be loaded in a .sumocfg configuration file or interactively through the Open Shapes option in the File-menu.

Shapes and POIs can be located based on their unique ID and their appearance can be customized as well.

Showing Background Images

In addition to changing the appearance of simulated structures, one may also load additional background images ("decals") into SUMO-GUI. For this, open the visualisation settings using Colorwheel.gif and - if you are not yet here - choose the "Background" panel (figure 1.1). You will see a table with following columns: picture file, center x, center y, width, height, and rotation.

Decals gui.gif

Fig. 1.1: The decals GUI.

Now, if you click into the first row of the "picture file" column, you should be able to enter the complete path of an image file. Confirming the path by pressing RETURN should force SUMO-GUI to load and display the file below the road network, as shown in figure 1.2.

Background example.gif

Fig. 1.2: Example of a background image (decal).

Currently, SUMO-GUI may load .gif, .png and .bmp files. If built with gdal-support further formats such as .tif are also usable.

Now, you may position/stretch/rotate the image using the columns center x, center y, width, height, and rotation.

When setting the column relative to 1, position and size values will be taken as screen-relative pixel values instead of network-relative meter values.

After aligning your decals, you can save them using the "Save Decals" button located in the dialog. Accordingly, previously saved decals can be loaded by pressing the "Load Decals" button.

When defining decals in XML a single line which looks like this:

<decal filename="background.gif" centerX="550.00" centerY="1530.00" width="64.00" height="64.00" rotation="0.00"/>

The following attributse are supported

Attribute Name Value Type Description
filename path (string) picture file, the full name of the background image
centerX float center x, the x-position of the center of the image in network coordinates (in meters)
centerY float center y, the y-position of the center of the image in network coordinates (in meters)
width float The width of the image in network coordinates (in meters)
height float The height of the image in network coordinates (in meters)
rotation float The angle of the image in degrees
layer float The layer at which the image in drawn in meters over ground
screenRelative bool relative, whether the position and size are pixel coordinates relative to the screen rather then the network coordinates
centerZ float The z-position of the center of the object in network coordinates (in meters), only used in 3D visualization instead of layer
tilt float The tilt angle of the object, only used in 3D visualization
roll float The roll angle of the object, only used in 3D visualization
Note:
The contents of a decal-configuration can also be embedded in a view-settings file and thus loaded on startup. see Configuration Files

Transparency

All image files in the visualization support transparency. For vehicles, pois and polygons, this transparency can be set dynamically by changing the color via TraCI and setting the alpha-channel.

All objects that have their color set (via input files or visualisation settings) support (Red,Green,Blue,Alpha) color values.

Configuration Files

SUMO-GUI uses the same configuration files as SUMO. The recognized options can be obtained by calling sumo --help or you save a configuration file with default settings by calling sumo --save-template <file> --save-commented. The option --gui-settings-file is specific to SUMO-GUI. It allows you to load a previously saved gui-settings file. The easiest way to obtain a gui-settings file is via the View Settings-Dialog Open viewsettings editor.gif. Simply modify the settings and save Save.gif.

Note, that the gui-settings-file obtained this way only contain information about the viewport (zoom and offset), delay, breakpoints and decals if the corresponding check-boxes are activated before saving. When you are done the configuration files should look like below:

example.sumocfg

<configuration>
    <net-file value="yournetwork.net.xml"/>
    <gui-settings-file value="gui-settings.cfg"/>
</configuration>

gui-settings.cfg

<viewsettings>
    <scheme name="...
       ...
    </scheme>

    <viewport zoom="200" x="100" y="-100"/>
    <delay value="42"/>
    <decal filename="background.gif" centerX="550.00" centerY="1530.00" width="64.00" height="64.00" rotation="0.00"/>
    <breakpoint value="42"/>
    <breakpoint value="1337"/>
</viewsettings>

Alternatively, you can manually add a breakpoint-file definition to your settings

<viewsettings>
 ...
 <breakpoints-file value="breakpoints.txt"/>
</viewsettings>

A file, suitable for loading breakpoints can be obtained by setting breakpoints in the gui and using the menu-option for saving (Edit->Edit Breakpoints->save).

You may either load example.sumocfg using the open simulation-dialog or by using the command-line sumo-gui -c example.sumocfg.

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

It is also possible to reference a predefined scheme by it's name alone:

<viewsettings>
    <scheme name="real world"/>
</viewsettings>

Screenshots

It is possible to take screenshots at predefined times by adding <snapshot> elements to the configuration:

<viewsettings>
    <snapshot file="myScreenshot.png" time="42"/>
</viewsettings>

Multiple Views

Using the (NewView.gif)-button, multple viewing windows onto the same simulation can be opened. The visualization settings can be set independently for each view. The viewing windows can be managed using the Windows menu in the main menu bar.

When passing multiple files to the SUMO-option --gui-settings-file, one viewing window is opened for each file at the start of the simulation.

3D Visualization

When SUMO-GUI was compiled with OSG (OpenSceneGraph) support an additional (NewView.gif)-button is present which can be used to open a 3D-View.

Caution:
The 3D-Visualization is highly experimental
.

An pre-compiled windows version for testing is available here.

Usage Examples

Visualizing Shapes and Points of Interest

see Using additional Polygons and POIs within the Simulation

Showing routes and route-related information

Investigating internal edges and lanes

Internal Edges define the movements across an intersection. By default they are hidden behind the shape of the junction to give a prettier visualisation. Occasionally it is of interest to understand which internal lane corresponds to which movement as their IDs may be referenced in the output or in error messages. The following visualisation settings are helpful:

  • Junction settings:
    • disable draw junction shape
    • show internal edge name
    • show internal junction name
    • show link junction index (to see the correspondence between IDs and link indices)
  • Edge settings:
    • Exaggerate width by 0.1 (otherwise the shapes overlap which makes it hard to understand them)
    • Color by selection (coloring individual lanes makes it easier to understand geometry before and after internal junctions)

Visualizing edge-related data

Weight Files that are loaded into SUMO-GUI can be visualized by setting the edge coloring by loaded weight. By using edgeData-output files as weight-files and setting option --weight-attribute to departed or arrived various traffic attributes can be visualized. This can also be used to visualized the edge-probability files generated by randomTrips.py.

When using SUMO-GUI for visualizing weight files with values that change over time (files containing multiple intervals) and no vehicles are being simulated, it is helpful to load the simulation with option --end to avoid premature simulation end while advancing the time to visualize the changing values (by 'running' the simulation).

Note:
Weight files can also be generated by equipping vehicles with device.rerouting and setting option --device.rerouting.output.


This page was last modified on 13 December 2018, at 08:16.