-
Notifications
You must be signed in to change notification settings - Fork 615
[PWGCF] : Flow Event Plane #13740
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
[PWGCF] : Flow Event Plane #13740
Conversation
Updated PID response includes a new PIDResponse header and added several configurable parameters for track selection and analysis. Adjusted histogram definitions and gain calibration logic to use the current run number.
|
O2 linter results: ❌ 0 errors, |
victor-gonzalez
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.
Please, rebase your changes to the latest version
PWGCF/Flow/Tasks/flowEventPlane.cxx
Outdated
| #include "Common/DataModel/Multiplicity.h" | ||
| #include "Common/DataModel/PIDResponseTOF.h" | ||
| #include "Common/DataModel/PIDResponseTPC.h" | ||
| #include "Common/DataModel/PIDResponse.h" |
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.
Please, rebase your changes to the latest version of O2Physics
This is rolling back a previous centralized change
PWGCF/Flow/Tasks/flowEventPlane.cxx
Outdated
| struct CorrHistContainer { | ||
| TH2F* hGainCalib; | ||
| std::array<std::array<THnSparseF*, 1>, 4> vCoarseCorrHist; | ||
| std::array<std::array<TProfile*, 4>, 4> vFineCorrHist; | ||
| } CorrHistContainer; |
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.
Names are cheap in programming!
I would suggest Correction instead of Corr to distinguish from Correlation
| getResoFlow(tracks, vSP); | ||
|
|
||
| // Update run number | ||
| lRunNum = cRunNum; |
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.
Any reason for needing two?
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.
Yes, for the current implementation to fetch correction factors once per run, it is required. I couldn't think of any other way.
Updated PID response includes a new PIDResponse header and added several configurable parameters for track selection and analysis. Adjusted histogram definitions and gain calibration logic to use the current run number.