-
Notifications
You must be signed in to change notification settings - Fork 186
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
Universal DistToDestination metric #2042
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work!
"Route computed in reverse direction from point_b to " | ||
f"point_a resulting in negative distance: {dist_tot}." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we should be using the term displacement
rather than distance here since distance
can also mean magnitude from a point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the route from point_b
to point_a
is not straight, then the route distance
will be longer than the displacement
between point_b
and point_a
. So rephrasing the error message as "Route computed in reverse direction from point_b to point_a resulting in negative displacement: {dist_tot}." also sounds a little awkward as the displacement might be shorter than the printed dist_tot
.
DistToDestination
metric is now computed by summing the(i) off-route distance driven by the vehicle from its last on-route position, and
(ii) the distance to goal from the vehicle's last on-route position.