Conversation
Collaborator
Author
|
So I ran a couple comparisons between current Quality differenceHere is the average gap to optimal solution on the usual CVRP/VRPTW instance sets in both situations.
So on top of avoiding embarrassing crossings in the provided solutions, adding this operator does have a contribution on overall quality. The impact on PDPTW and bigger VRPTW instances looks somehow similar, maybe with less overall impact as the problem size grow. Timing differenceThat's the nice part: there is virtually no difference in average computing times on those benchmarks, this PR being even sometimes slightly faster. I see two reasons for this:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Fixes #706
Tasks
cvrp::IntraTwoOptvrptw::IntraTwoOptCHANGELOG.md