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

Adjust Eval::operator< #914

Closed
jcoupey opened this issue Apr 5, 2023 · 0 comments · Fixed by #963
Closed

Adjust Eval::operator< #914

jcoupey opened this issue Apr 5, 2023 · 0 comments · Fixed by #963
Milestone

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Apr 5, 2023

Internal evaluation is currently based on cost values, which are usually derived from duration via vehicles costs.per_hour factors.

But think of a situation where a user is providing custom costs matrices to model the cost of "reaching out to a given zone", typically when taking subcontracting costs into account. Then all costs for locations from zone A to zone B will be identical, and all intra-zone costs will be zero. In this situation comparing based on cost only means all intra-zone orderings in routes have the same cost so we can provide an arbitrary (bad duration-wise) ordering for zones.

So we should compare Eval instances based first on cost, then on durations in case of draw, which makes sense anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant