Thank you for the careful investigation!
The problem is now fixed in the dev version:
https://github.com/eclipse/sumo/issues/13384
Am Di., 6. Juni 2023 um 17:15 Uhr schrieb Stefano Bonasera <
stefano.bonas...@gmail.com>:
> Thank you for the answer.
>
> After leaving this problem for a few
Thank you for the answer.
After leaving this problem for a few months I had to recently get back at
it and it is still unsolved. However, I found out that:
1) The headway problem at the moment of loading a saved state only happens
for vehicles of type "rl"
2) The 'rl' vehicle is added to the
> Please let me know if I am missing anything.
Reproducing the example requires the sumocfg (sumo.cfg in your log) and all
files that are referenced within the sumocfg.
> although I do .subscribe() and .subscribeLeader() for the rl vehicle,
these are not showing in the log file.
The following
The cascading types are expected when you call functions that change vType
attributes on a singe vehicle (i.e. traci.vehicle.setLength). In order to
change the property only for a single vehicle, the type is cloned every
time.
However, the reported information is insufficient to understand the
Hi Jakob,
Thanks for the prompt reply.
What I see in the vType in the saved file for both types is:
I tried to play around also with the minGap (only difference I see between
these two vTypes) and that is indeed influencing the headway - only for the
rl type:
1) If minGap = 0: I get the
This sounds as if something goes wrong when loading the type of the rl
vehicle. Please look into the saved state file and post the line that
defines the vType of the rl vehicle.
Am Do., 23. März 2023 um 14:47 Uhr schrieb Stefano Bonasera <
stefano.bonas...@gmail.com>:
> Hello,
>
> I use sumo
Hello,
I use sumo 1.16, interfacing with python.
I noticed a weird behavior when loading and saving state and I hope you can
help me explain the motivation behind it
I have only two types of vehicles in my simulation (other and rl). Assume
the rl vehicle has as a lead vehicle, say, "flow_15"
