Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Driving distance does not take into account loops in routes #4642

Closed
m-kro opened this issue Sep 25, 2018 · 1 comment

Comments

@m-kro
Copy link
Contributor

commented Sep 25, 2018

Precondition:
A vehicle travels on a route which contains the same edge twice. For example, it goes around a circle for n times before traveling to other parts of the network.
Problem:
The user queries the remaining driving distance of the route through traci.vehicle.getDrivingDistance(). The result only takes into account the position of the vehicle but not how often it has already passed the current edge (=the actual position in the route). For this reason, the driving distance may result longer than it actually is.

@namdre namdre self-assigned this Sep 25, 2018

@namdre

This comment has been minimized.

Copy link
Contributor

commented Sep 25, 2018

@m-kro It would be great if you could add a failing test to sumo/tests/complex/traci/pythonApi/bugs

behrisch added a commit that referenced this issue Sep 28, 2018

@namdre namdre closed this in 23ea8cc Sep 28, 2018

m-kro added a commit to m-kro/sumo that referenced this issue Oct 3, 2018
Copy fix for eclipse#4642 to traci.vehicle.getDrivingDistance2D
Signed-off-by: m-kro <m.barthauer@t-online.de>
behrisch added a commit that referenced this issue Oct 3, 2018
Merge pull request #4660 from m-kro/distance2D
Copy fix for #4642 to traci.vehicle.getDrivingDistance2D
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.