Fix zero-cost edges in the TSP example#229
Merged
Merged
Conversation
03d2e54 to
21a7535
Compare
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.
The br17 example reports 87 instead of the published optimum of 39 because it treats every zero in the distance matrix as a missing edge. br17 contains valid off-diagonal zero-cost edges.
Remove that extra filtering and let
circuitenforce the tour. The example then reaches 39; the two smaller instances retain costs 2276 and 22.Checks:
tsptarget;git diff --check.Closes #151.