[PWGHF] [xic0omegac0] Updated candidate creator & candidate selector#16042
[PWGHF] [xic0omegac0] Updated candidate creator & candidate selector#16042jinhyunni wants to merge 7 commits intoAliceO2Group:masterfrom
Conversation
|
O2 linter results: ❌ 0 errors, |
| int pdgIdOfV0DauPos, pdgIdOfV0DauNeg, pdgIdOfBach, pdgIdOfCharmBach; | ||
| int pdgIdOfAntiV0DauPos, pdgIdOfAntiV0DauNeg, pdgIdOfAntiBach, pdgIdOfAntiCharmBach; | ||
| int pdgIdOfV0, pdgIdOfCascade, pdgIdOfCharmBaryon; | ||
|
|
||
| // Track PID - Used in DCAFitter | ||
| int trackPidOfCascade; | ||
|
|
||
| // Mass of daughter tracks & V0s & cascades & charm baryons; | ||
| float massOfV0DauPos, massOfV0DauNeg, massOfBach, massOfCharmBach; | ||
| float massOfV0, massOfCascade, massOfCharmBaryon; | ||
| float massOfV0DauPos, massOfV0DauNeg, massOfCharmBach; | ||
| float massOfV0, massOfCascade; |
There was a problem hiding this comment.
Always initialise in declaration.
There was a problem hiding this comment.
Hi @vkucera,
They are set to be initialized within init function.
Do they still needed to be initialized at the moment of declaration?
There was a problem hiding this comment.
Yes, it can be just with {}, but it should always be there.
There was a problem hiding this comment.
I wasn't aware of that issue.
Thanks for letting me know!
I've added commit to incorporate your comment.
There was a problem hiding this comment.
Hi @vkucera,
If you have a moment, could you have a look at the updated PR and check if everythis looks good on your side?
There was a problem hiding this comment.
I don't know why you linked a formatting PR and why you think it fixed O2 linter warnings.
There was a problem hiding this comment.
Because after merging that formatting PR, all the checks were passed.
I double checked by running o2_linter.py locally to see if any warnings or errors occur.
Or am I missing something?
There was a problem hiding this comment.
The formatting PR just removed trailing spaces on one line. That cannot change the result of the O2 linter check.
What do you have locally on these lines?
PWGHF/TableProducer/candidateSelectorToXiPiQa.cxx:298
PWGHF/TableProducer/candidateSelectorToXiPiQa.cxx:445
There was a problem hiding this comment.
Sorry, I've missed that part...
I checked and fixed name of the functions located on the lines you've provided.
After making changes, I've checked locally and saw linter passes without any warnings.
I learnd a new thing about formatting PR. Thanks:)
Hi @jinhyunni, why you remove |
Hi @zhangbiao-phy. |
Hi @jinhyunni, I see your point. maybe we can try to address this at a later stage, when you subscribe to the table. You can refer to the solution used for the 3-prong case here: O2Physics/PWGHF/TableProducer/treeCreatorLcToPKPi.cxx Lines 1165 to 1166 in 482efe6 continue here, the final tree will become very large. This issue will be even more pronounced in Pb–Pb analyses.
|
Thanks for your thoughtful comment on this update. |
Please consider the following formatting changes to AliceO2Group#16042
|
And sorry for accidentaly closing this PR without appropriate consultion. |
|
Hi @zhangbiao-phy. |
Hi @jinhyunni, Thanks! Looks good to me! |
Thanks :) |
candidateCreatorXic0Omegac0Qa:
massOfBach,massOfCharmBaryoncandidateSelectorToXiPiQa:
continuestatement inside candidate loop