-
Notifications
You must be signed in to change notification settings - Fork 628
Cascade Task Update #2885
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
Cascade Task Update #2885
Conversation
1. Mult axis 2. TPC pt axis 3. FIx Nevents precision bug 4. Nch vs Signal in FT0M/FV0A
Please consider the following formatting changes to #2885
ChiaraDeMartin95
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.
Could you please also add the possibility to select the zvertex of the collision in the cascpostprocessing? Haveing a configurable variable would be perfect.
| AxisSpec rapidityAxis = {200, -2.0f, 2.0f, "y"}; | ||
| AxisSpec centFT0MAxis = {100, 0.0f, 100.0f, "FT0M (%)"}; | ||
| ConfigurableAxis centFT0MAxis{"FT0M", | ||
| {VARIABLE_WIDTH, 0., 0.01, 0.1, 0.5, 1, 5, 10, 15, 20, 25, 30, 35, 40, 50, 70, 100}, |
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.
could you please add 0.05 and 45, 55, 60, 65, 75 and so on in bins of 5% up to 100? We might want to have a look at lower multiplicities as well at a certain point.
| registry.add("hDCAxy_BefCut", "hDCAxy_BefCut", HistType::kTH2F, {{400, -0.2, 0.2, "DCAxy"}, {150, 0.0, 15.0, "p_{T} (GeV/c)"}}); | ||
| registry.add("hDCAxy_AfterCut", "hDCAxy_AfterCut", HistType::kTH2F, {{400, -0.2, 0.2, "DCAxy"}, {150, 0.0, 15.0, "p_{T} (GeV/c)"}}); | ||
| registry.add("hNchMultFT0M", "hNchMultFT0M", HistType::kTH2F, {{150, 0.f, 150.f, "N_{ch}"}, {10000, 0.f, 10000.f, "FT0M signal"}}); | ||
| registry.add("hNchMultFV0A", "hNchMultFV0A", HistType::kTH2F, {{150, 0.f, 150.f, "N_{ch}"}, {10000, 0.f, 10000.f, "FV0A signal"}}); |
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.
have you checked if these intervals cover the whole distribution?
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.
for the FT0M and FV0A I just inherited the max from O2Physics/Common/Tasks/multiplicityQa.cxx. Nevertheless, it could be more reasonable to have kTProfile in Mult axis to get the average signal in FT0M/FV0A for each multiplicity in the event: that will help with the binning issue (at least for the Mult axis). For the Nch one - idk what to expect in VHM events, so we can put 1k for it if you agree.
PWGLF/Tasks/cascpostprocessing.cxx
Outdated
| AxisSpec centFT0MAxis = {100, 0.0f, 100.0f, "FT0M (%)"}; | ||
| AxisSpec centFV0AAxis = {100, 0.0f, 100.0f, "FV0A (%)"}; | ||
| ConfigurableAxis centFT0MAxis{"FT0M", | ||
| {VARIABLE_WIDTH, 0., 0.01, 0.1, 0.5, 1, 5, 10, 15, 20, 25, 30, 35, 40, 50, 70, 100}, |
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.
same comment as before
| registry.fill(HIST("hCascCosPA"), candidate.pt(), candidate.casccospa()); | ||
| registry.fill(HIST("hV0CosPA"), candidate.pt(), candidate.v0cospa()); | ||
| registry.fill(HIST("hCascRadius"), candidate.pt(), candidate.cascradius()); | ||
| registry.fill(HIST("hV0Radius"), candidate.pt(), candidate.v0radius()); |
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.
I think you can add the second axis (pt) for all topological variables. Maybe you can define ptAxisTopoVar with bins of 200 MeV each, and not 50 MeV each (50 bins in total from 0 to 10 GeV).
Please consider the following formatting changes to #2885
* BranchInit 1. Mult axis 2. TPC pt axis 3. FIx Nevents precision bug 4. Nch vs Signal in FT0M/FV0A * Upd Mult and Cut hists * Please consider the following formatting changes * del isFT0MforMC for rec. hists * Upd 1. Implement Chiara's suggestions 2. hNAssocCollisions 3. hNContributorsCorrelation for the case when there're 2 rec. collisions for the 1 gen. * Please consider the following formatting changes --------- Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
* BranchInit 1. Mult axis 2. TPC pt axis 3. FIx Nevents precision bug 4. Nch vs Signal in FT0M/FV0A * Upd Mult and Cut hists * Please consider the following formatting changes * del isFT0MforMC for rec. hists * Upd 1. Implement Chiara's suggestions 2. hNAssocCollisions 3. hNContributorsCorrelation for the case when there're 2 rec. collisions for the 1 gen. * Please consider the following formatting changes --------- Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
* BranchInit 1. Mult axis 2. TPC pt axis 3. FIx Nevents precision bug 4. Nch vs Signal in FT0M/FV0A * Upd Mult and Cut hists * Please consider the following formatting changes * del isFT0MforMC for rec. hists * Upd 1. Implement Chiara's suggestions 2. hNAssocCollisions 3. hNContributorsCorrelation for the case when there're 2 rec. collisions for the 1 gen. * Please consider the following formatting changes --------- Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
* BranchInit 1. Mult axis 2. TPC pt axis 3. FIx Nevents precision bug 4. Nch vs Signal in FT0M/FV0A * Upd Mult and Cut hists * Please consider the following formatting changes * del isFT0MforMC for rec. hists * Upd 1. Implement Chiara's suggestions 2. hNAssocCollisions 3. hNContributorsCorrelation for the case when there're 2 rec. collisions for the 1 gen. * Please consider the following formatting changes --------- Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
Uh oh!
There was an error while loading. Please reload this page.