-
Couldn't load subscription status.
- Fork 33
Implement Charged Candidate Maker (PFA1b) #2124
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
base: add-track-cluster-subtraction-pfa-one
Are you sure you want to change the base?
Implement Charged Candidate Maker (PFA1b) #2124
Conversation
for more information, see https://pre-commit.ci
…-candidate-maker-pfa-one
This PR applies the include-what-you-use fixes as suggested by https://github.com/eic/EICrecon/actions/runs/18477497612. Please merge this PR into the branch `add-charged-candidate-maker-pfa-one` to resolve failures in PR #2124. 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>
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.
Not sure about the particle/ namespace instead of reco/, but we can have it.
Thanks! My thinking here is that PFAlpha is the starting point for broader PF efforts, so, over time, this namespace will be filled with more algorithms. One thing to consider might be to move some of our existing PF algorithms into this namespace: that way all of our particle reconstruction algorithms are in one place. This would be a step towards factoring the existing |
Briefly, what does this PR introduce?
This PR implements the
ChargedCandidateMakeralgorithm. This algorithm ingests track-cluster matches and converts them to charged particle candidates, i.e.edm4eic::ReconstructedParticleswith only select relations filled.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?
No.
Does this PR change default behavior?
No.