-
Notifications
You must be signed in to change notification settings - Fork 345
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
Work on reducing operators scope #1008
Conversation
dcb29c4
to
8f548cf
Compare
8f548cf
to
0e81b2a
Compare
After a routine check on HVRP instances, I noticed the solution quality were highly degraded with this PR. This makes sense because the pruning argument based on geometric consideration somehow hold only if we assume homogeneous costs between routes. In order to keep the benefit of the improvements here but avoid missing too many interesting moves, we should fine-tune and only prune route pair moves if the associated vehicles are "similar". |
ce72251
to
f093c83
Compare
Turns out most of the HVRP instances (the DLP dataset) do not provide point locations... As a result the bbox checks where discarding all moves. Nevertheless only pruning for homogeneous vehicle pairs is still a good idea since otherwise we're loosing too much quality. |
Issue
Fixes #509
Tasks
*Exchange
SwapStart
(Reverse)TwoOpt
CHANGELOG.md