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
Comments
did you use traci? |
Just use the python to generate the E3 dectector according to my network configuration and combine it to my sumcfg file |
I can confirm the crash |
Hi, Jakob,
If I would like to run the simulation with the E3 installed in the network.
How could I do that?
Best regards!
Jane
…On Sat, Nov 17, 2018 at 6:40 AM Jakob Erdmann ***@***.***> wrote:
Closed #4803 <#4803> via 3046562
<3046562>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://mailtrack.io/trace/link/06405344a884e04cbe725ec950c209ba3cfff16e?url=https%3A%2F%2Fgithub.com%2Feclipse%2Fsumo%2Fissues%2F4803%23event-1972767784&userId=3378854&signature=09c45d098864cfea>,
or mute the thread
<https://mailtrack.io/trace/link/107c599a0c5126c21b37a60ac0b708df64b81408?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAlfu-fqjqOnjxIDYisySGAPadgide3sdks5uwAPAgaJpZM4YiAH_&userId=3378854&signature=adc007ea68e08d3f>
.
|
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? |
Download the latest development version where the bug which causes termination is fixed: |
Thank you Jakob,I would try it later!
…On Wed, Nov 21, 2018 at 1:51 AM Jakob Erdmann ***@***.***> wrote:
Download the latest development version where the bug which causes
termination is fixed:
http://sumo.dlr.de/wiki/Downloads#Nightly_Snapshots
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4803 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Alfu-es0R2MD4Iwt2auhg8Ir4vacsCFhks5uxQYRgaJpZM4YiAH_>
.
|
Jakob, I found I run the different scenairo to check the bug!
The simulation* still could not* end at the expected end time!
I have downloaded the
[image: image.png]
and let the new files replace the old one. Is it right to do that?
Is there something wrong that I did?
[image: image.png]
Best regards!
Jane
…On Wed, Nov 21, 2018 at 8:48 AM Jane Cheung ***@***.***> wrote:
Jakob, I have checked the scenario, the simulation end at the expected
time and all things are right! Thank you so much!
Jane
On Wed, Nov 21, 2018 at 5:48 AM Jane Cheung ***@***.***>
wrote:
> Thank you Jakob,I would try it later!
>
> On Wed, Nov 21, 2018 at 1:51 AM Jakob Erdmann ***@***.***>
> wrote:
>
>> Download the latest development version where the bug which causes
>> termination is fixed:
>> http://sumo.dlr.de/wiki/Downloads#Nightly_Snapshots
>> <https://mailtrack.io/trace/link/621753fd9a1be60f79b703a5b138cb4beebff97a?url=http%3A%2F%2Fsumo.dlr.de%2Fwiki%2FDownloads%23Nightly_Snapshots&userId=3378854&signature=d1b44de11c23597b>
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <https://mailtrack.io/trace/link/2c7158b93ce3608ab822050d584f070209617bc1?url=https%3A%2F%2Fgithub.com%2Feclipse%2Fsumo%2Fissues%2F4803%23issuecomment-440569228&userId=3378854&signature=7155be6ea98bdd02>,
>> or mute the thread
>> <https://mailtrack.io/trace/link/757013210b3e827c504141fa4b6669776acc3251?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAlfu-es0R2MD4Iwt2auhg8Ir4vacsCFhks5uxQYRgaJpZM4YiAH_&userId=3378854&signature=dc13d7d49e859fcf>
>> .
>>
>
|
sorry. I found another crash. Closing the ticket was premature. |
I've fixed another issue and your original dataset runs to completion. Please try again with the very latest version. |
Thank you Jabok,
Happy holiday~
…On Thu, Nov 22, 2018 at 3:47 PM Jakob Erdmann ***@***.***> wrote:
I've fixed another issue and your original dataset runs to completion.
Please try again with the very latest version.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4803 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Alfu-Z02TF3kk7JEBCB9xpqPERDk0haVks5uxxtkgaJpZM4YiAH_>
.
|
when you run 'where sumo' what does it say? |
Hi, Jakob, I have removed the sumo1.0.1 and reload the last one from the Nightly_Snapshots; performs emergency braking with decel=-9.00 wished=4.50 severity=1.00, time=26469.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! |
What‘s more, the emergency brakes of vehicles were not printed in Log. |
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 |
Below is the updated output after run the command of
''sumo''
-------------------------------------------
Eclipse SUMO Version v1_0_1+0795-316a7cead1
Build features: Windows-6.3.9600 AMD64 MSVC 18.0.40629.0 Proj GUI
Copyright (C) 2001-2018 German Aerospace Center (DLR) and others;
http://sumo.dlr.de
<https://mailtrack.io/trace/link/e4b335378453dd89bdc021fe1d6b011e39af5098?url=http%3A%2F%2Fsumo.dlr.de&userId=3378854&signature=ba68b9b8817f51db>
License EPL-2.0: Eclipse Public License Version 2 <
https://eclipse.org/legal/epl-v20.html
<https://mailtrack.io/trace/link/2187d2232ad369d5299d2346f3bfc9c617a890ee?url=https%3A%2F%2Feclipse.org%2Flegal%2Fepl-v20.html&userId=3378854&signature=b3825c66ccdfd7ed>
Use --help to get the list of options.
Best regards!
…On Mon, Nov 26, 2018 at 2:06 PM Jakob Erdmann ***@***.***> wrote:
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
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://mailtrack.io/trace/link/83ce462a0cf184270efa4fb9cec541f31b56b2b3?url=https%3A%2F%2Fgithub.com%2Feclipse%2Fsumo%2Fissues%2F4803%23issuecomment-441779272&userId=3378854&signature=9f5999e7253978b4>,
or mute the thread
<https://mailtrack.io/trace/link/2d07fbf0f87059205fedb454aa361fe0e436476c?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAlfu-TVgjz0ib1XJ-E87zsw0BHcdXJE1ks5uzEm-gaJpZM4YiAH_&userId=3378854&signature=d248394bd998e1e3>
.
|
This version should be able to run your scenario without crashing. |
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, |
Thanks Jakob! |
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
The text was updated successfully, but these errors were encountered: