-
Notifications
You must be signed in to change notification settings - Fork 613
[Common] TPC interface: skipTPCOnly auto mode, fix Run 2 bug #13604
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
Conversation
…evaluation on/off
|
O2 linter results: ❌ 21 errors, |
|
tested to work just fine, going to review to allow for code test via CI |
alibuild
left a comment
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.
Auto-approving on behalf of @ddobrigk.
Pull request was converted to draft
alibuild
left a comment
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.
Auto-approving on behalf of @ddobrigk.
…Group#13604) Co-authored-by: David Dobrigkeit Chinellato <david.dobrigkeit.chinellato.cern.ch>
…Group#13604) Co-authored-by: David Dobrigkeit Chinellato <david.dobrigkeit.chinellato.cern.ch>
This PR:
Adds a new mode "-1" to the skipTPCOnly configurable of the TPC PID functionality, such that it will calculate the dEdx for TPC-only tracks only in case specific tasks that require it are detected. The rationale is to allow for a single hyperloop core service wagon to be used while still saving the CPU required to evaluate the Nsigma for TPC-only if not needed.
Fixes a Run 2 crash by correctly capturing the attempt to access a CCDB object for Run 2 converted data.