Re: [sumo-user] Count Veh on Induction Loop

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Historically, inductionLoops in SUMO always had length=0 so there wasn't the need to distinguish between vehicles that passed the entry and vehicles that occupied the loop.

If this is what you need, you may find it more convenient to use laneAreaDetector instead of inductionLoop. 

Am Mi., 2. Nov. 2022 um 09:44 Uhr schrieb till.wenke <till.wenke@xxxxxxxxxxxxxxxxxxxxxxxxxx>:

Hi, I am working with induction loops for monitoring and speed adaption.

I came across some inconsistencies between the generated xml output (XML) of induction loops and the values that can be retrieved via traci.induction_loop api (API).

So it would be great to fix it or help me in case I make wrong assumptions.

1) via API we do getLastStepVehicleNumber which is as far as I can say the number of cars on the loop. but here https://sumo.dlr.de/docs/TraCI/Induction_Loop_Value_Retrieval.html it says that it corresponds to nVehEntered from XML. Here https://sumo.dlr.de/docs/Simulation/Output/Induction_Loops_Detectors_%28E1%29.html it also says that nVehEntered gives all vehicles on the loop. But this is not the case (testable with a long induction loop eg length='50') - I would say the nVehEntered really just gives us the number of vehicles that passed the entry of the loop. Would be great to align the metrics or even have nVehEntered, nVehDetected (exited), nVehNumber (on) in both XML and API.

2) I can image the with the metrics that are currently available for XML and API one can compute the ones that are not available in one of them but it would be more convenient to really have the same metrics in both (eg. flow (just in XML), time_since_detection (just in API).

Cheers

Till

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user