-
Notifications
You must be signed in to change notification settings - Fork 30
Add Lowq2 track association #1775
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: main
Are you sure you want to change the base?
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Need to fix some memory access issues https://github.com/eic/EICrecon/actions/runs/14180103934/job/39724400039?pr=1775#step:8:1153 |
Capybara summary for PR 1775
|
8d615ab
to
fe949e1
Compare
fe949e1
to
6c90821
Compare
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.
Don't see any problems with this, although, I admit, I understand only so much of this. Would be nice to have a unit test for this to check some basic cases. Other than that, there are few comments and questions from me.
@@ -17,18 +17,16 @@ | |||
namespace eicrecon { | |||
|
|||
using FarDetectorLinearProjectionAlgorithm = | |||
algorithms::Algorithm<algorithms::Input<edm4eic::TrackSegmentCollection>, | |||
algorithms::Algorithm<algorithms::Input<edm4eic::TrackCollection>, | |||
algorithms::Output<edm4eic::TrackParametersCollection>>; |
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.
(Just a thought)
For Acts tracking, we actually output projections as TrackSegments.
src/factories/fardetectors/FarDetectorLinearProjection_factory.h
Outdated
Show resolved
Hide resolved
Co-authored-by: Dmitry Kalinkin <[email protected]>
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Briefly, what does this PR introduce?
Reorganization of the FarDetectorLinearTracking to allow Track-Particle associations to be produced for the Low-Q2 Tagger.
Not quite the whole picture but this PR should stand alone before the associations are propagated to the Post-ML tracks and injected into the common tracking flow.
There are lots of alternative approaches to this, the current one here felt like the least ugly (assuming it works).
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?
Changes the output of FarDetectorLinearTracking to an edm4eic::Track rather than edm4eic::TrackSegment. At a later date both might be produced as the TrackSegment contains TrackPoints which are equivalent to a missing 3D measurement.