-
Notifications
You must be signed in to change notification settings - Fork 29
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(dRICH): CentralCKFTrajectories
-> CentralCKFActsTrajectories
#880
Conversation
As long as there is nothing in the default output files that relies on the DRICH code, we are going to keep breaking the DRICH unintentionally because it is not tested for... So, you could (have) avoid(ed) this by adding |
|
#829 is on my list to review and merge this week... |
https://eicweb.phy.anl.gov/EIC/benchmarks/reconstruction_benchmarks/-/merge_requests/293 is also ready (I just realized I never marked it "ready"), but is only useful if someone routinely checks the plots. This particular track propagation issue just showed up as empty plots. |
We have several benchmarks that fail if there are no entries when there are entries expected. |
We should add this feature, this MR is just a starting point. I keep trying to push @chchatte92 to improve the benchmarks, since he now does quite a lot more by hand :) |
Absolutely. Let's say, I will add at least these three-four features by next week to the benchmarks
Does it sound ok? |
Testing this fix with benchmarks using eic/drich-dev#98 since it seems I never added them to the CI config. And adding benchmarks to the CI config with https://eicweb.phy.anl.gov/EIC/benchmarks/reconstruction_benchmarks/-/merge_requests/306 |
CentralCKFTrajectories
-> CentralCKFActsTrajectories
CentralCKFTrajectories
-> CentralCKFActsTrajectories
eic/drich-dev#103 blocks me from testing eta and momentum scans, but at least for single fixed momenta, dRICH PID appears to be recovered after this PR. |
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.
Yup.
e058fed
to
c62bf05
Compare
Briefly, what does this PR introduce?
Fix dRICH track propagation by using
CentralCKFActsTrajectories
instead ofCentralCKFTrajectories
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?
yes, should restore functionality to dRICH