Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Removed maxHits condition from ScoreBasedAmbiguitySolver #3676

Merged
merged 3 commits into from
Oct 1, 2024

Conversation

Ragansu
Copy link
Contributor

@Ragansu Ragansu commented Oct 1, 2024

The maxHits setting was used in cuts and ambiscore. For the ambiscore this was essential

But maxHits often set low for the ambiscore to work well. This would mean there will be removal of tracks in high eta region due to cuts. Now the maxHits 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

Copy link

github-actions bot commented Oct 1, 2024

📊: Physics performance monitoring for ee14aa4

Full contents

physmon summary

Copy link
Contributor

@Corentin-Allaire Corentin-Allaire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good for me.

@AJPfleger AJPfleger added this to the v37.0.0 milestone Oct 1, 2024
Copy link

sonarcloud bot commented Oct 1, 2024

@kodiakhq kodiakhq bot merged commit da1d846 into acts-project:main Oct 1, 2024
42 checks passed
@github-actions github-actions bot removed the automerge label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants