-
Notifications
You must be signed in to change notification settings - Fork 613
[PWGHF] store PID info in 3-prong candidate table and propagate it to analyses. #10984
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
|
O2 linter results: ❌ 24 errors, |
1d634d1 to
5a5fa5e
Compare
|
@fgrosa I should have addressed everything for Lc. Other 3 prongs have to be adapted. |
Please consider the following formatting changes to AliceO2Group#10984
Please consider the following formatting changes to AliceO2Group#10984
|
@fgrosa Lc, D+ and Ds should be fine. |
|
Also D* should be fine. |
|
@fgrosa now also Xic->pKpi is in place. If you agree, I open it for review |
|
Hi @mfaggin, thanks a lot! There are still a few files to be modified: |
Please consider the following formatting changes to AliceO2Group#10984
Please consider the following formatting changes to AliceO2Group#10984
thanks a lot @fgrosa, by mistake I overlooked the change of Instead, for the resonance candidate creator I do not understand what I shall change. In fact, I only see the explicit query of PID information for the bachelor track/V0, and not for the daughters of 2-prong, 3-prong, or D* candidates. What am I missing? |
Hi @mfaggin, you are indeed right! |
thanks for the confirmation @fgrosa . Then, in principle there should be everything. |
Please consider the following formatting changes to AliceO2Group#10984
vkucera
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.
Minor
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 @mfaggin.
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
… analyses. (AliceO2Group#10984) Co-authored-by: Mattia Faggin <mfaggin@cern.ch> Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
Continuation of #7805