[WQ] Drop duplicate boundaries instead of making them unique.#1917
Merged
[WQ] Drop duplicate boundaries instead of making them unique.#1917
Conversation
evetion
changed the title
SouthEndMusic
approved these changes
Oct 24, 2024
Collaborator
SouthEndMusic
left a comment
SouthEndMusic
left a comment
There was a problem hiding this comment.
I was convinced that this is good (:
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
2 participants
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.
Found while debugging the LHM model. A tracer was added, but didn't show up in Delwaq because the boundary list (bndlist) was shifted after duplicate UserDemand edges.
Also added more information to the generated.csv files for debugging.