lcodeca/mostscenario

Monaco SUMO Traffic (MoST) Scenario

Monaco SUMO Traffic (MoST) Scenario

Contacts: Lara CODECA [[email protected]], Jerome HAERRI [[email protected]]

This project is licensed under the terms of the GPLv3 license.

MoST Scenario is meant to be used with SUMO (Simulator of Urban MObility).

• The master is tested with SUMO 1.14.0
• In case there are problems with multi-threading, check that Issue #4518 has been solved in your target version.

Please refer to the SUMO wiki for further information on the simulator itself.

How to cite it: BibTeX

L. Codeca, J. Härri, "Towards Multimodal Mobility Simulation of C-ITS: The Monaco SUMO Traffic Scenario" VNC 2017, IEEE Vehicular Networking Conference November 27-29, 2017, Torino, Italy.

or

L. Codeca, J. Härri, "Monaco SUMO Traffic (MoST) Scenario: A 3D Mobility Scenario for Cooperative ITS" SUMO 2018, SUMO User Conference, Simulating Autonomous and Intermodal Transport Systems May 14-16, 2018, Berlin, Germany

How To

MoST Scenario can be lunched directly with its configuration file.

• sumo -c most.sumocfg or run.sh from the scenario folder.

See tools HOWTO for further details on how to chance and rebuild the scenario.

Overview

Mobility Example

(click on the image for the video)

Traffic Light Example

(click on the image for the video)

Public Transportation Example

(click on the image for the video)

The master is tested with Eclipse SUMO Version 1.14.0

(Build features: Darwin-21.5.0 arm64 Clang 13.1.6.13160021 Release FMI Proj GUI SWIG GDAL FFmpeg OSG GL2PS)

Performance: 
Performance:
 Duration: 3407.14s
 Real time factor: 10.566
 UPS: 352602.634584
 UPS-Persons: 49427.018430
Vehicles:
 Inserted: 46842
 Running: 31
 Waiting: 0
Teleports: 99 (Jam: 29, Yield: 55, Wrong Lane: 15)
Emergency Stops: 6
Persons:
 Inserted: 45000
 Running: 26
 Jammed: 3865
Statistics (avg of 43356):
 RouteLength: 7217.10
 Speed: 6.98
 Duration: 6892.62
 WaitingTime: 52.51
 TimeLoss: 148.27
Bike Statistics (avg of 3455):
 RouteLength: 1876.49
 Speed: 4.53
 Duration: 428.03
 WaitingTime: 35.13
 TimeLoss: 64.48
Statistics (avg of 46811):
 DepartDelay: 0.37
Pedestrian Statistics (avg of 31421 walks):
 RouteLength: 451.37
 Duration: 387.66
 TimeLoss: 58.73
Ride Statistics (avg of 45216 rides):
 WaitingTime: 40.07
 RouteLength: 6058.59
 Duration: 609.21
 Bus: 5967
 Bike: 3455 

Users

• Vincent Terrier, Aerospace System Design Laboratory, Georgia Institute of Technology, Atlanta, GA 30332-0105
• Tianshu Chu, Civil and Environmental Engineering, Stanford University

If you are using MoST Scenario, or its tools to generate a new one, we would gladly add you to the list. You can send an e-mail to [email protected] with your name and affiliation (if any).

mostscenario's Issues

Runtime exception while running most.out.sumocfg

SUMO Version: 1.2
OS: Ubuntu 16.04
Python Version: 3.5.2

Error when running MoST with SUMO 1.20

Dear MoSTScenario developers,

thank you for offering this great traffic scenario. I tried to run it with SUMO 1.20 under Ubuntu 18.04.

An error displayed in the terminal, after Step #18425.50

t9zLet/sumo-1.2.0+dfsg1/src/microsim/cfmodels/MSCFModel.cpp:776: double MSCFModel::maximumSafeStopSpeedEuler(double, double) const: Assertion
'h <= g + NUMERICAL_EPS' failed.

Do you have some advice to solve this problem?

Thank you in advance!

Best regards,
Kailin

Exectuing MoSTS simulation in Sumo 1.3.1

I am executing the scenario in Sumo 1.3.1, just cloned the master. Is it posible to make a simulation like the ones shown in the videos? I mean with cars, lorries and more traffic? In my simulation are only (apparently) used buses and trains.

Missing scenario/in/route/most.commercial.rou.xml

most.sumocfg references a file called "in/route/most.commercial.rou.xml", but it doesn't seem to exist in the repo. Calling "sumo -c 'most.sumocfg" with SUMO version 1.0 thus doesn't work, unless the reference to this file is removed. The error given is:

Error: The route file 'in/route/most.commercial.rou.xml' is not accessible.
Quitting (on error).

Is it valid to run this scenario without commercial.rou.xml?

Gridlock related to strange car to bus stop interaction

Hello everyone!
Issue:
The network congestion is irrealistic and vehicles can't move at all.

Sumo versions:
I tried running MoST for different versions of Sumo (based on the issues and commits): 1.9.2/0.26.0/1.19.0/1.14.1

I am having the same issue as previous issues available on LuST and MoST repos. The versions changed the intensity of it, but irrealistic scenarios were always created. I know the data is synthetic but one of the versions should work well with the synthetic data and produce realistic behavior (based on my understanding). When having a deeper look, I realized that huge queues are created by vehicles stopping next to a bus stop:

A wider view would be:

The vehicles will later disappear suddenly.

How to help?

It would be great if someone could provide me a Sumo version that wouldn't create this issue.
Traci changed after Sumo 1.0 so optimally the working version would be >1.0 and would recreate the peak hours and off-peak hours shown in the papers. Thank you in advance!!

invalid access from non-pedestrian lane

A recently added sumo error message exposes problems with the access definitions:
Warning: Ignoring invalid access from non-pedestrian lane '153656_1' in busStop '131018'.
(access should target the sidewalks if they exist).

MoSTS connections

Hello,
I am using the MoSTS scenario along with Sumo and Flow framework. I am having an issue when Flow tries to read the '*.net.xml' since it crashes when trying to read some connections defined in this file. The Flow code supposes that a connection that goes from a lane to an internal link, for example:
<connection from="-152476" to=":131254_w0" fromLane="0" toLane="0" dir="s" state="M"/>
should have an attribute 'via', but it hasn't. I have look for this restriction in sumo documentation but all I found is this: " it should be taken into account that a connection with an internal lane follows a special pattern. For example when lane 1_f_0 needs to be connected to 1_t_0 through 1_v_0, the following connection entries exist: [from=1_f_0, to=1_t_0 via=1_v_0] and [from=1_v_0 to=1_t_0]. If the latter is omitted, SUMO will not load the network. It will also not load if next to the necessary connections a connection [from=1_f_0 to=1_v_0] exists.", I don't know if this applies to the case exposed for the upper conection or it is just a bug in Flow code.
Thanks a lot,
Alberto

No elevation for railways

The railway has always elevation 0.
Given that it is always ground level or in tunnels, I don't consider it a major issue.
If/when I'll have data, it will be fixed.

MoST with SUMO 1.9.2

Hi,

we would like to run the MoST scenario with a more recent version of SUMO (1.9.2).

We noticed that at certain locations, traffic is piling up at intersections using 1.3.1 which does not happen in 1.9.2.

First example:
With SUMO 1.3.1:

and with SUMO 1.9.2:

Second example:
With SUMO 1.3.1:

and with SUMO 1.9.2:

The output of SUMO 1.9.2 says:

Eclipse SUMO sumo Version 1.9.2
 Build features: Linux-5.12.9-arch1-1 x86_64 GNU 11.1.0 Release Proj GUI
SWIG GDAL FFmpeg OSG
 Copyright (C) 2001-2021 German Aerospace Center (DLR) and others;
https://sumo.dlr.de
....
Simulation ended at time: 50400.00
Reason: The final simulation step has been reached.
Performance:
 Duration: 3203.15s
 Real time factor: 11.2389
 UPS: 374543.147099
 UPS-Persons: 51272.532918
Vehicles:
 Inserted: 46842
 Running: 32
 Waiting: 0
Teleports: 52 (Jam: 15, Yield: 32, Wrong Lane: 5)
Emergency Stops: 2
Persons:
 Inserted: 45000
 Running: 26
 Jammed: 2560
Statistics (avg):
 RouteLength: 6839.22
 Speed: 6.92
 Duration: 6406.78
 WaitingTime: 35.84
 TimeLoss: 121.52
 DepartDelay: 0.45
Pedestrian Statistics (avg of 31421 walks):
 RouteLength: 450.72
 Duration: 385.63
 TimeLoss: 57.15
Ride Statistics (avg of 45216 rides):
 WaitingTime: 38.11
 RouteLength: 6073.44
 Duration: 589.52
 Bus: 5967
 Bike: 3455

Currently, we are unsure why this might happen and which of the behavior shown above is actually the desired one.
Do you have an idea what might be the cause of this behavior?
Also, is 1.3.1 the most recent version of SUMO capable to run this scenario?

Thank you and kind regards
Alexander

Edit: This was tested with the current master (7cee150)