[PWGLF] Added signal/event loss corrections

[sawankumawat]

No description provided.

[github-actions]

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

[dmallick2]

@sawankumawat please fix o2linter error

[sawankumawat]

@sawankumawat please fix o2linter error

The only o2linter error is "Assign the value to a clearly named variable or constant". But then I have to create many variables in the code at every place, which will not look good. @vkucera Please suggest

[vkucera]

@sawankumawat please fix o2linter error

The only o2linter error is "Assign the value to a clearly named variable or constant". But then I have to create many variables in the code at every place, which will not look good. @vkucera Please suggest

Hi @sawankumawat @dmallick2 , you are not supposed to "create many variables in the code at every place", on the contrary, you are supposed to define a few meaningful variables to replace the hard-coded numbers. In your case, it seems you only need a constant for the rapidity cut and for the number of daughters.

Btw, you have 4 other categories of errors which should also be fixed. You are hard-coding masses and PDG codes and reinventing the phi range constraints. Please use the existing functionalities as the linter suggests.

[sawankumawat]

@sawankumawat please fix o2linter error

The only o2linter error is "Assign the value to a clearly named variable or constant". But then I have to create many variables in the code at every place, which will not look good. @vkucera Please suggest

Hi @sawankumawat @dmallick2 , you are not supposed to "create many variables in the code at every place", on the contrary, you are supposed to define a few meaningful variables to replace the hard-coded numbers. In your case, it seems you only need a constant for the rapidity cut and for the number of daughters.

Btw, you have 4 other categories of errors which should also be fixed. You are hard-coding masses and PDG codes and reinventing the phi range constraints. Please use the existing functionalities as the linter suggests.

Hi @vkucera Thank you for the suggestion. I have solved all the linter errors now.

[alibuild]

Error while checking build/O2Physics/o2 for b5bba79 at 2025-07-29 09:57:

## sw/BUILD/O2Physics-latest/log
/sw/SOURCES/O2Physics/12293-slc9_x86-64/0/PWGLF/Tasks/Resonances/higherMassResonances.cxx:1383:36: error: comparison of integer expressions of different signedness: 'std::vector<bool>::size_type' {aka 'long unsigned int'} and 'std::array<int, 6>::value_type' {aka 'int'} [-Werror=sign-compare]
/sw/SOURCES/O2Physics/12293-slc9_x86-64/0/PWGLF/Tasks/Resonances/higherMassResonances.cxx:1388:25: error: comparison of integer expressions of different signedness: 'std::vector<bool>::size_type' {aka 'long unsigned int'} and 'std::array<int, 6>::value_type' {aka 'int'} [-Werror=sign-compare]
ninja: build stopped: subcommand failed.

Full log here.

[sawankumawat]

@dmallick2 @vkucera I think now all the things are resolved. Thanks for your help. Please approve and enable auto merging.
Thank you

[vkucera]

@sawankumawat Thanks for implementing the comments.