Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

simulation involving E3 detectors does not terminate #4803

Closed
JaneCheung opened this issue Nov 15, 2018 · 22 comments

Comments

@JaneCheung
Copy link

commented Nov 15, 2018

Hi, after I used the generateTLSE3Detectors.py to generate the E3 detectors for the network ,
the simulation by adding the E3 could not terminate and escape the simulation.
Why does it happen ? How could we add the E3 detector and finish our simulation?
the attachment is the log file of the simuation.
log.log
1
2

@namdre namdre changed the title simualtion involving E3 detectors does not terminate simulation involving E3 detectors does not terminate Nov 15, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 15, 2018

did you use traci?
can you provide example input files?

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 16, 2018

Just use the python to generate the E3 dectector according to my network configuration and combine it to my sumcfg file
bug.zip

@namdre namdre self-assigned this Nov 16, 2018
@namdre namdre added a:SUMO bug labels Nov 16, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 16, 2018

I can confirm the crash

namdre added a commit that referenced this issue Nov 17, 2018
@namdre namdre closed this in 3046562 Nov 17, 2018
@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 19, 2018

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 20, 2018

Jakob, if I would like to use the scenario to do the simulation, how could I avoid the terminate? Decrease the number of views that would be inserted in the network? Or other measures?

@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 21, 2018

Download the latest development version where the bug which causes termination is fixed:
http://sumo.dlr.de/wiki/Downloads#Nightly_Snapshots

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 21, 2018

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 21, 2018

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 21, 2018

@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 22, 2018

sorry. I found another crash. Closing the ticket was premature.

@namdre namdre reopened this Nov 22, 2018
namdre added a commit that referenced this issue Nov 22, 2018
namdre added a commit that referenced this issue Nov 22, 2018
namdre added a commit that referenced this issue Nov 22, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 22, 2018

I've fixed another issue and your original dataset runs to completion. Please try again with the very latest version.

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 22, 2018

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 24, 2018

tim 20181124145231
tim 20181124145105
I have downloaded the file“sumo-msvc12x64-git. zip”, and replace the old version. In my computer the simulation still could not get the expected the final termination.

@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 26, 2018

when you run 'where sumo' what does it say?
when you run 'sumo' by itself what is the output (I'm interested in the exact version specifier)
It should be something like Eclipse SUMO Version v1_0_1+0793-2e8063c695

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 26, 2018

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 26, 2018

Hi, Jakob, I have removed the sumo1.0.1 and reload the last one from the Nightly_Snapshots;
However, there are lot of warnings while I was simulating the scenario, like :


performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26469.00.
Warning: Vehicle '11687' performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26477.00.
Warning: Vehicle '16176' performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26483.00.
Warning: Vehicle '14224' performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26483.00.
Warning: Vehicle '16279' performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26488.00.
Warning: Vehicle '15866' performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26498.00.
Warning: Vehicle '15068' performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26498.00.


This warning has not been presented while I was using the original version of SUMO, how could I deal with this problem?

Best regards!

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 26, 2018

What‘s more, the emergency brakes of vehicles were not printed in Log.

@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 26, 2018

  1. The request command was 'where sumo' not 'where is sumo'
    2,3) Your version was old and did not include the fix.
  2. either the zip or msi version should work if the paths are set correctly

The version with emergency warnings is newer. If you post the output of 'sumo' (the version info) I can tell you if it's the correct one.

The emergency warnings were added last week to report suspicious driving behavior. The driving behavior itself did not change. Some of these warnings may be due to bugs in SUMO and these will be fixed. The warnings could also indicate bad model parameters or bad traffic light configurations. You can disable the warnings using the option --emergencydecel.warning-threshold 1.1

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 26, 2018

@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 27, 2018

This version should be able to run your scenario without crashing.

@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 27, 2018

Note, that I've fixed one more crash related to E3 detectors yesterday that is not included in the version you have. This crash only occurs if vehicles leave the simulation without passing e3 exit detectors. Since this does not happen in your scenario, the issue (#4845) does not affect you but it might be relevant for future scenarios.

regards,
Jakob

@JaneCheung

This comment has been minimized.

Copy link
Author

commented Nov 27, 2018

Thanks Jakob!

@namdre namdre closed this Mar 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.