The recommended way to obtain aggregated data is via xml outputs (i.e. tripinfo-output for aggregation on the vehicle level). Tripinfo-output is flushed in every simulation step so you might even parse this at runtime if really needed. The typical use case of traci is for runtime manipulation of the simulation rather than collection of aggregated data. Subscribing to arrived vehicles can be useful to remove them from the set of vehicles that you are currently manipulating.
regards, Jakob Am Mi., 17. Nov. 2021 um 17:53 Uhr schrieb T Eenachtacht < [email protected]>: > > Hi, > > Subscription to arrived vehicles is a trigger to collect aggregated data > from those vehicles at the end of their simulation life such as total > distance travelled (getDistance), accumulated waiting time, and their > number of stops. Pretty standard stuff for a traffic simulation. Alas, the > vehicle id is no longer known upon arrival. > > What is the intended use of subscribing to arrived vehicles then, and how > can i get aggregated vehicle data in their last time steps? > > Thanks, Bart > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
