-
Notifications
You must be signed in to change notification settings - Fork 32
fix: Add ImagingTopoCluster layer mode within same layers #1999
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
fix: Add ImagingTopoCluster layer mode within same layers #1999
Conversation
In this PR, a new phiz layermode is introduced in the Imaging Topological Clustering Algorithm to group hits both within the same layer and across different layers.
The impact of these changes is studied using a 2-photon simulation, and the corresponding plots are attached. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid initialization order errors (https://github.com/eic/EICrecon/actions/runs/17133996414/job/48605273777?pr=1999#step:7:624) and to avoid having to sometimes have diff first and sometimes same, this reorders the config ordering so the algorithms will always have same first, then diff next.
May need changes in FHCAL or ZDC, I didn't verify that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Diff looks good to me. Capybara report shows no changes to ZDC, as expected. https://eicrecon.epic-eic.org/pr/1999/capybara/rec_dis_18x275_minQ2=1000_craterlake_18x275/index.html#HcalFarForwardZDCClusters
…wyu) (#2056) This PR applies the include-what-you-use fixes as suggested by https://github.com/eic/EICrecon/actions/runs/17303800492. Please merge this PR into the branch `Test-Layermodes-within-same-layers-for-ImagingTopo-Clusters` to resolve failures in PR #1999. Auto-generated by [create-pull-request][1] [1]: https://github.com/peter-evans/create-pull-request Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
for more information, see https://pre-commit.ci
…wyu) (#2056) This PR applies the include-what-you-use fixes as suggested by https://github.com/eic/EICrecon/actions/runs/17303800492. Please merge this PR into the branch `Test-Layermodes-within-same-layers-for-ImagingTopo-Clusters` to resolve failures in PR #1999. Auto-generated by [create-pull-request][1] [1]: https://github.com/peter-evans/create-pull-request Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
for more information, see https://pre-commit.ci
b5e8f4f
to
9959c45
Compare
Rebased for #2057. |
#2015) ### Briefly, what does this PR introduce? This PR modifies the unscoped enum `ESigmaMode` to a scoped enum, and avoids the implicit integer conversion by correcting the `operator<<` signature. Before this fix, the output was `0` or `1` (since the incorrectly-signatured `operator<<` is not used); after this fix, the output is `abs` or `rel`. The scoping of the enum adds a layer of safety since the symbol `abs` could previously shadow the standard function `std::abs`. This aligns with the enabled clang-tidy check `cppcoreguidelines-use-enum-class`, https://clang.llvm.org/extra/clang-tidy/checks/cppcoreguidelines/use-enum-class.html. ### What kind of change does this PR introduce? - [x] Bug fix (issue: #1999 (comment), but fails to compile #1999 (comment)) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No. ### Does this PR change default behavior? No. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Briefly, what does this PR introduce?
Added Layer Modes to the helper function to group hits within the same layer for ImagingTopoCluster
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
Does this PR change default behavior?