-
Notifications
You must be signed in to change notification settings - Fork 30
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: convert TrackParamTruthInit to use DD4hep units #1198
fix: convert TrackParamTruthInit to use DD4hep units #1198
Conversation
f730f4d
to
db4a59e
Compare
e45de40
to
ce75dfc
Compare
ce75dfc
to
cb4d891
Compare
No diffs. |
Is that with running capybara locally? |
Might be that webpages are out of sync. Last CI run eg https://github.com/eic/EICrecon/actions/runs/7503697056/job/20430403477 has no diffs. |
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 LGTM. We should be transitioning to edm4eic::unit
, but now is not the time.
Definitely we should move to |
Briefly, what does this PR introduce?
Units are set (via command line or config files) assuming a certain unit system. We have chosen DD4hep for this in all other cases (in part because it comes with a parser). Having one algorithm use Acts units is potentially confusing since distances may be passed in the wrong units.
This PR converts TrackParamTruthInit to store the config variables in DD4hep units, and modifies the algorithm itself to interpret the config in DD4hep units. No changes are expected to the output.
No values are specified in the factory or in the plugin, so this is the only change that should be needed.
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.