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]>
An: "Sumo project User discussions" <[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
