| Re: [sumo-user] WG: AW: multi-lane area detector (e2) value retrieval bug |
Hi Manos,
on my side it looks fine. Are you sure you use the fresh libsumo version? The change in source code is not related to libsumo/TraCI itself but to data storage of detectors, so there shouldn't be any difference on how you access the data.
Best regards
Mirko
-----Original-Nachricht-----
Betreff: Re: [sumo-user] WG: AW: multi-lane area detector (e2) value retrieval bug
Datum: 2023-10-31T16:41:41+0100
Von: "manos kampitakis" <mankampitakis@xxxxxxxxx>
An: "Mirko Barthauer" <m.barthauer@xxxxxxxxxxx>, "Sumo project User discussions" <sumo-user@xxxxxxxxxxx>
Hi Mirko,It seems that the problem is resolved in Traci, but it persists in libsumo.Best regards,Manos
Στις Παρ 20 Οκτ 2023 στις 1:07 μ.μ., ο/η Mirko Barthauer via sumo-user <sumo-user@xxxxxxxxxxx> έγραψε:_______________________________________________
Hi Manos,
you are absolutely right. The problem has been fixed in the Github repo (see issue #13966). Please build sumo from Github source or wait for the development version binaries of tomorrow. Thank you for reporting!
Best regards
Mirko
-----Original-Nachricht-----
Betreff: Re: [sumo-user] multi-lane area detector (e2) value retrieval bug
Datum: 2023-10-19T19:03:49+0200
Von: "manos kampitakis" <mankampitakis@xxxxxxxxx>
An: "Mirko Barthauer" <m.barthauer@xxxxxxxxxxx>
Mirko I found what is the fault. If you set file="NUL" inside the e2 detector definition, the last interval occupancy does not work (returns always zero). This is not the case for e1 detectors where last interval occupancy works in both cases (set "NUL" or give an xml path). If you still need a sample scenario let me know.
Στις Πέμ 19 Οκτ 2023 στις 7:10 μ.μ., ο/η Mirko Barthauer <m.barthauer@xxxxxxxxxxx> έγραψε:Hi Manos,
I cannot reproduce the problem. Our TraCI tests regarding lane area detectors do not show anything similar. Would you be willing to share a sample scenario and your TraCI script?
Best regards
Mirko
-----Original-Nachricht-----
Betreff: [sumo-user] multi-lane area detector (e2) value retrieval bug
Datum: 2023-10-19T15:09:34+0200
Von: "manos kampitakis via sumo-user" <sumo-user@xxxxxxxxxxx>
An: "Sumo project User discussions" <sumo-user@xxxxxxxxxxx>
Hi all,I have created a corridor where I have placed a multi-lane area detector (e2) with a period of 300s and I want to retrieve last interval occupancy via traci or libsumo. In a previous project, I have done the same with induction loops (e1) and it works as follows. If the detector has a period of 300s for example, the interval occupancy is the running mean within the period of 300s. When the simulation time modulo (%) the period (300s) is 0 the interval occupancy becomes zero and the last interval occupancy value is updated. Within the period the last interval occupancy remains constant. It seems that there is some bug in multi-lane area detectors when it comes to the last interval occupancy value retrieval because it always remains zero. I have provided a printed output for 898 seconds (1 - 899s). The first column is the simulation time, the second is the last step occupancy, the third is the interval occupancy and the fourth is the last interval occupancy. The results are the same for traci and libsumo.Best regards,Manos
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user