ITSMFT::Clusterer: Optionally drop huge clusters #13808
Merged
+38
−29
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.
@shahor02
The implementation is obvious.
Taking as example Layer0, stave 5, the difference is visible.
Before:
After:
There are of course much worse scenarios.
See the print of the full layer.
Before:
After:
Unfortunately this does not really improve much the situation with the reconstruction, as the total number of clusters does changes of orders of ~1%.
Some of the very large clusters will do the dashed clusters effect, as I was mentioning earlier (will look for an example), and there is no way of not saving them with this.
Maybe there is still good reason to keep the "development".