Apply blob threshold configuration in charge solving #186
Conversation
This file contains 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
3 tasks
|
Looks good to me. |
brettviren
added a commit
that referenced
this pull request
Jan 9, 2023
This fixes the 'vestigial wire' bug (#186) but I've yet to reproduce the original missed corner inclusion.
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 blob threshold configuration parameter is no longer ignored.
When set to zero the
depo-ssi-viztest outputs all blobs so that the number of blobs matches the "depo blob fill" branch produces.Even with the measure threshold set to zero a few measures get removed compared to the "depo blob fill" branch. I guess some measures are negative?