[PWGCF] framework for FemtoVsFlow

[wenyaCern]

Overview

I've created a simple framework for calculating femtocorrelation functions with divided qₙ-vectors for Event-shape engineering of flow measurements, building on femtoUniverse (and incorporating small parts of femtodream). The analysis wants to estimate the relation between femtoRadii vs v2.

Why a New Framework

Key updates to the data model necessitated this:

1. The collision table and track in FemtoDerived.h in Datamodel now includes q-vector information.
2. The particle table has added PID checks using TOF-beta, improving particle species discrimination.
3. More flow calculation functionalities will be added to the framework for the analysis.

[github-actions]

O2 linter results: ❌ 2 errors, ⚠️ 0 warnings, 🔕 10 disabled

[wenyaCern]

fix formatting

[victor-gonzalez]

Please, keep it as draft until it gets reviewed/approved

Also, for the new files, follow linter and MegaLinter recommendations

The fact that linter and MegaLinter recommendations are not enforced is because that will require to stop any new change until the full O2Physcs code is adapted to those recommendations

But new files had to adhere to them. It is in the benefice of everyone

Thanks!!

[victor-gonzalez]

@wenyaCern, thanks for moving forward this functionality!
Are you aware that the femto data model is being redefined in order to have a single femto derived data format able to be used by all femto analyses?
Have you been in touch with the femto PAG coordinators for exposing your needs?
The aim is to have a single derived data production for femto analysis because storage space is a scarce resource and we cannot afford having multiple derived data productions unless it were really really necessary

[wenyaCern]

Dear Victor,
Thanks a lot for your information and suggestion.

For this analysis, using the current femto-derived data format is impossible, as the analysis procedure in Task only reserves the filtered tracks by the table producer, while the calculation for flow requires inclusive hadrons. Events will be separated by the information of flow and that flow information will be transferred to analysis tasks. Considering the above reasons, I prefer to create a new data format by adding flow information in the data-driven, which will be isolated and not affect the current femto analysis.

I'm fixing the O2 linter and MegaLinter issues now. Hope you can consider my update and thanks a lot for that!

Best regards,
Wenya

[victor-gonzalez]

Dear Victor, Thanks a lot for your information and suggestion.

For this analysis, using the current femto-derived data format is impossible, as the analysis procedure in Task only reserves the filtered tracks by the table producer, while the calculation for flow requires inclusive hadrons. Events will be separated by the information of flow and that flow information will be transferred to analysis tasks. Considering the above reasons, I prefer to create a new data format by adding flow information in the data-driven, which will be isolated and not affect the current femto analysis.

I'm fixing the O2 linter and MegaLinter issues now. Hope you can consider my update and thanks a lot for that!

Best regards, Wenya

Dear Wenya,
I didn't ask you to use the current femto-derived data format. I know as today it is not feasible
What I asked you is if you have exposed your needs at the femto PAG and the people that is restructuring the femto derived data model for having such needs considered in the femto derived data data model (copying here @ariedel-cern and @lauraser)
Unfortunately each analysis cannot produce their own derived data because there is not enough storage space available for that

[wenyaCern]

Dear Victor, Thanks a lot for your information and suggestion.
For this analysis, using the current femto-derived data format is impossible, as the analysis procedure in Task only reserves the filtered tracks by the table producer, while the calculation for flow requires inclusive hadrons. Events will be separated by the information of flow and that flow information will be transferred to analysis tasks. Considering the above reasons, I prefer to create a new data format by adding flow information in the data-driven, which will be isolated and not affect the current femto analysis.
I'm fixing the O2 linter and MegaLinter issues now. Hope you can consider my update and thanks a lot for that!
Best regards, Wenya

Dear Wenya, I didn't ask you to use the current femto-derived data format. I know as today it is not feasible What I asked you is if you have exposed your needs at the femto PAG and the people that is restructuring the femto derived data model for having such needs considered in the femto derived data data model (copying here @ariedel-cern and @lauraser) Unfortunately each analysis cannot produce their own derived data because there is not enough storage space available for that

Dear Victor,
Thanks for your suggestions! I'll discuss with Femto PAG for the function in the redefined data format of femto in the future.

[wenyaCern]

The O2 linter errors have been fixed.
Rest O2 linter errors are in CMakeLists.txt, reviewing of workflow naming.

The derived data contains the qn bin information, which is the only thing changed from the femtoUniverse framework.

[victor-gonzalez]

@wenyaCern@shouqiye This is still not ready for being merged
I am in contact with @ariedel-cern on how to proceed with it
It changes the femto derived data model and require additional derived data which can only be used by this analysis

[victor-gonzalez]

Please, keep it as draft for the time being