The reported travel times are computed but using the average vehicle speed on the lane at that simulation step. Due to traffic light cycles, this speed can be quite low and thus the reported travel time is very high. The issue should disappear when averaging speeds over multiple time steps (averaging travel times is not a good idea).
Am Mi., 2. Sept. 2020 um 16:53 Uhr schrieb Taylor Oliveira < [email protected]>: > Hi all, > > I have a question about the traci.lane.getTraveltime(self, laneID) > function, > > I’m testing a 4x4 grid net with 200m edges and 100m attached edges with a > 500 veh/hour for OD pair over 3600 steps (attached files). > > looking at the simulation with sumo-gui there is not much congestion, > > using TraCI, every 5 simulation steps, I call traci.lane.getTraveltime() > and I’m getting big numbers for some of the lanes, such as 30000 - 40000, > > looking at the documentation, this is supposed to be the estimated lane > travel time in seconds, but, for me, it doesn’t make sense to take 30000 > seconds to cross a 200m lane, > > Is the value right? How is it calculated (I’ve searched but didn’t find > anything)? > > Please, give me some light :) > > Thank you and best regards, > > Taylor > _______________________________________________ > 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
