| Re: [sumo-user] Issues with emergency braking and action-step-length |
Hello Jakob, community, I rerun my simulation with SUMO 1.1.0 (official zip version) and I still have all the emergency braking issues. I used emergencydecel.warning-threshold 1.1 and they do disappear, but I would like to know if there is something wrong with my vehicles behavior. Additionally, what is the proper way to use action-step-length? I thought of having action-step-length of 1s and step-length of .25s but I'm having an incredible number of collisions. Is it possible that it's due to https://github.com/eclipse/sumo/issues/2581 given that I'm using the sublane model? Am I simply using it wrong? Are there some guidelines in order to proper configure these parameters? I just would like to be sure that my mobility is behaving in a reasonable way and I don't have misconfigured parameters. Attached you can find: ├── [4.6K] basic.vType.xml ├── [4.0K] action-step-length --> plenty of collisions everywhere │ ├── [ 30M] most.sim.log │ └── [2.5K] most.sumocfg ├── [4.0K] no-action-step-length --> plenty of emergency braking │ ├── [2.3M] most.sim.log │ └── [2.5K] most.sumocfg └── [4.0K] warning-threshold_1.1 --> emergency braking disappears ├── [642K] most.sim.log └── [2.6K] most.sumocfg All the Best, Lara On Thu, 22 Nov 2018 13:18:37 +0100 Jakob Erdmann <namdre.sumo@xxxxxxxxx> wrote: > Yes and no. > The warnings are new but they only warn you about stuff that were always > happening since 1.0.0 (from that version onwards, vehicle are allowed to > perform emergency deceleration). > Some of those decelerations are due to bugs (discovered since introducing > the warning). > If fixed some of the bugs this week so just upgrade to the very latest > version. > > I think we'll get rid of most of the warnings by the time 1.1 is released > in december. > You can supress the warning by setting option > --emergencydecel.warning-threshold 1.1 > > regards, > Jakob > > btw: your sumo version specifier seems wrong because the warning was > introduced 7 days ago but the commit hash is from 24 days ago. > > Am Do., 22. Nov. 2018 um 13:07 Uhr schrieb Lara CODECA < > lara.codeca@xxxxxxxxxx>: > > > Dear all, > > > > I'm using Debian Unstable and Eclipse SUMO Version v1_0_1+0470-da7d0832e7 > > (Build features: > > Linux-4.18.0-2-amd64 x86_64 GNU 8.2.0 Release Proj GUI GDAL FFmpeg OSG > > GL2PS SWIG). > > > > I'm running my usual simulation scenario > > https://github.com/lcodeca/MoSTScenario but from SUMO > > Version 5345f89a38 (the last time I tested it) and v1_0_1+0470-da7d0832e7 > > something has changed, > > because I have a very long list of > > > > Warning: Vehicle ... performs emergency braking with decel=-9.00 > > wished=4.50 severity=1.00, time=... > > See attachment for the simulation log. > > I suppose I need to change my usual simulation parameters, but I don't > > know where to start. > > Can I have some directions? > > > > All the Best, > > Lara > > > > -- > > Lara CODECA > > Postdoc > > Tel : 04.93.00.81.51 > > > > EURECOM > > Campus SophiaTech > > http://www.eurecom.fr/ > > _______________________________________________ > > sumo-user mailing list > > sumo-user@xxxxxxxxxxx > > To change your delivery options, retrieve your password, or unsubscribe > > from this list, visit > > https://www.eclipse.org/mailman/listinfo/sumo-user > > -- Lara CODECA Postdoc Tel : 04.93.00.81.51 EURECOM Campus SophiaTech http://www.eurecom.fr/
Attachment:
SUMO110_MoST_Emergency_Decel.zip
Description: Zip archive