Uh oh!
There was an error while loading. Please reload this page.
PWGHF: Fix for Signal status in MC Rec in D0-hadron correlations and implement event mixing - #3103
Conversation
Please consider the following formatting changes to AliceO2Group#3103
vkucera
left a comment
There was a problem hiding this comment.
Hi @samrangy , please
- fix the structure of the code (order of members),
- fix the naming (tasks and types),
- fix the types of the configurables to avoid unnecessary casting in filters
- fix hard-coded PDG codes
- fix hard-coded values of
signalStatus.
samrangy
commented
Jul 20, 2023
Hi @vkucera, thanks for your comments. Could you please elaborate the first two points? It would be helpful if you provide example. |
vkucera
commented
Jul 21, 2023
|
Please consider the following formatting changes to AliceO2Group#3103
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| {"hDeltaPhiPtIntSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + "entries", {HistType::kTH1F, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}}}}, | ||
| {"hCorrel2DPtIntSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + stringDeltaEta + "entries", {HistType::kTH2F, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {200, -10., 10.}}}}, | ||
| {"hCorrel2DVsPtSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + stringDeltaEta + stringPtD + stringPtHadron + "entries", {HistType::kTHnSparseD, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {nEtaBinsCorrelations, etaMinCorrelations, etaMaxCorrelations}, {10, 0., 10.}, {11, 0., 11.}}}}, // note: axes 3 and 4 (the pT) are updated in the init() | ||
| {"hCorrel2DVsPtSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + stringDeltaEta + stringPtD + stringPtHadron + "entries", {HistType::kTHnSparseD, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {nEtaBinsCorrelations, etaMinCorrelations, etaMaxCorrelations}, {10, 0., 10.}, {11, 0., 11.}, {9, 0., 9.}}}}, // note: axes 3 and 4 (the pT) are updated in the init() |
There was a problem hiding this comment.
Avoid repeating the same hard-coded axes.
There was a problem hiding this comment.
You still use e.g. {nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {200, -10., 10.} at many places. Define a single axis variable for each frequently used axis.
Uh oh!
There was an error while loading. Please reload this page.
Please consider the following formatting changes to AliceO2Group#3103
Please consider the following formatting changes to AliceO2Group#3103
Uh oh!
There was an error while loading. Please reload this page.
| /// D0-h correlation pair builder - for real data and data-like analysis (i.e. reco-level w/o matching request via MC truth) | ||
| void processData(aod::Collision const& collision, soa::Join<aod::Tracks, aod::TracksDCA>& tracks, soa::Join<aod::HfCand2Prong, aod::HfSelD0> const& candidates) | ||
| void processData(soa::Join<aod::Collisions, aod::Mults>::iterator const& collision, soa::Join<aod::Tracks, aod::TracksDCA>& tracks, soa::Join<aod::HfCand2Prong, aod::HfSelD0> const& candidates) |
There was a problem hiding this comment.
Still not fixed in many process functions.
| {"hDeltaPhiPtIntSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + "entries", {HistType::kTH1F, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}}}}, | ||
| {"hCorrel2DPtIntSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + stringDeltaEta + "entries", {HistType::kTH2F, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {200, -10., 10.}}}}, | ||
| {"hCorrel2DVsPtSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + stringDeltaEta + stringPtD + stringPtHadron + "entries", {HistType::kTHnSparseD, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {nEtaBinsCorrelations, etaMinCorrelations, etaMaxCorrelations}, {10, 0., 10.}, {11, 0., 11.}}}}, // note: axes 3 and 4 (the pT) are updated in the init() | ||
| {"hCorrel2DVsPtSignalRegion", stringDHadron + stringSignal + stringDeltaPhi + stringDeltaEta + stringPtD + stringPtHadron + "entries", {HistType::kTHnSparseD, {{nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {nEtaBinsCorrelations, etaMinCorrelations, etaMaxCorrelations}, {10, 0., 10.}, {11, 0., 11.}, {9, 0., 9.}}}}, // note: axes 3 and 4 (the pT) are updated in the init() |
There was a problem hiding this comment.
You still use e.g. {nPhiBinsCorrelations, phiMinCorrelations, phiMaxCorrelations}, {200, -10., 10.} at many places. Define a single axis variable for each frequently used axis.
Please consider the following formatting changes to AliceO2Group#3103
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
vkucera
commented
Aug 8, 2023
Please @samrangy do not force-push when you add commits! It is explicitly discouraged in the guidelines because it makes the review more complicated. |
alibuild
commented
Aug 8, 2023
Error while checking build/O2Physics/o2 for 5b7866a at 2023-08-08 11:32: Full log here. |
samrangy
commented
Aug 8, 2023
Every time I try to push it, I receive the following error, So I had to force it. [rejected] master -> master (fetch first) |
Please consider the following formatting changes to AliceO2Group#3103
vkucera
commented
Aug 8, 2023
That is because you modify your branch on GitHub with the formatting PR and then you try to push to the modified branch your local commits without updating your local branch first. You have to sync your local branch with the remote branch before pushing new commits to it. |
vkucera
commented
Aug 9, 2023
Thanks @samrangy |
…implement event mixing (AliceO2Group#3103)
…implement event mixing (AliceO2Group#3103)
…implement event mixing (AliceO2Group#3103)
…implement event mixing (AliceO2Group#3103)
No description provided.