[sumo-user] rerouteTraveltime Odd Behaviour

[Jonathan Harper <jonathan.v.harper@xxxxxxxxx>]

Hello,

I’ve ran into an odd behaviour in regards to traci.vehicle.rerouteTraveltime(). Sometimes, the best time will produce a route with an absurdly long (as in it will be 100x more than expected kind of long) estimated travel time (using the current travel times of the edges in the route) - unusually, this is not actually the ‘best’ travel time possible, other routes are actually available which are a far better which aren’t picked up by rerouteTravelTime. 

Do you know why this may be? Have you come across this before? If so, is there a fix to this issue?

Kind regards,
Jonathan