Hi Manos,
you are absolutely right. The problem has been fixed in the Github repo
(see issue #13966 <https://github.com/eclipse-sumo/sumo/issues/13966> ).
Please build sumo from Github source or wait for the development version
binaries
<https://sumo.dlr.de/docs/Downloads.php#sumo_-_latest_development_version>
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" <[email protected]>
An: "Mirko Barthauer" <[email protected]>
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 <
[email protected] <mailto:[email protected]> > έγραψε:
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" <[email protected]
<mailto:[email protected]> >
An: "Sumo project User discussions" <[email protected]
<mailto:[email protected]> >
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
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user
