refactor: Removed maxHits condition from ScoreBasedAmbiguitySolver #3676
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
maxHits
setting was used in cuts andambiscore
. For theambiscore
this was essentialBut
maxHits
often set low for theambiscore
to work well. This would mean there will be removal of tracks in high eta region due to cuts. Now themaxHits
is removed from cuts hence solving the issue. Since we have optional cuts users can add it back with independent value if needed.Ragansu Chakkappai