[Common/PWGHF]: store PID info in 2-prong candidate table and propagate it to analyses.#7805
Conversation
Please consider the following formatting changes to AliceO2Group#7805
fa42dfc to
1464526
Compare
|
thanks @fgrosa , I've implemented the 2 major comments of yours. I've also reverted the |
| hf_cand::NSigTpcPi0, hf_cand::NSigTpcKa0, | ||
| hf_cand::NSigTpcPi1, hf_cand::NSigTpcKa1, | ||
| hf_cand::NSigTofPi0, hf_cand::NSigTofKa0, | ||
| hf_cand::NSigTofPi1, hf_cand::NSigTofKa1, |
There was a problem hiding this comment.
In terms of generalisation of the common HF PID code, it would be better to have one table per prong index and per species, e.g. HfPidProng0Pi, HfPidProng0Ka, HfPidProng1Pi,...
|
Thanks a lot @vkucera for your suggestions. I've implemented them in the new commits.
|
|
Hi @mfaggin , I agree, in this case it is cleaner to force-push a history with only your work. |
- Needed tables added - TrackSelectorPID patch added to force the usage of a custom PID nSigma value (from 2-prong candidate table) - Add process functions via macro for combined TPC-TOF PID for 2-prong candidates - ML response class updated accordingly TODO: propagate it to the next pieces of the chain. Files to be adjusted: - [] TableProducer/derivedDataCreatorD0ToKPi.cxx - [] TableProducer/treeCreatorD0ToKPi.cxx - [] HFC/TableProducer/correlatorDMesonPairs.cxx - [] D2H/Tasks/taskd0.cxx - [] D2H/Tasks/taskBplus.cxx
- put the PID nsigma columns in another table, to be joined in analysis - use dynamic columns for nsigma combined
…f track-related data members.
ef70d15 to
7bec368
Compare
|
Thanks @vkucera , I've just addressed also your last comments. |
|
Hi @fgrosa @vkucera , I've just tried running the analysis aligning I attach also the full files used for the tests, for completeness. |
|
tagging also @ddobrigk since a file in |



@fgrosa here a possible development for the 2-prong only. 3-prong case not yet addressed