-
Notifications
You must be signed in to change notification settings - Fork 620
[PWGCF] Fixes and improvements for FemtoDream Cascades #9548
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
Conversation
gmantzar
commented
Jan 27, 2025
- Fixing selection bug in the Cascades
- Adding "BeforeCuts" and "AfterCuts" in the selection class of femtodream (for tracks and cascades only for now)
- chaning std::abs() to std::fabs() in the track and cascade selection
- adding the Omega selection flag in the producer task to select Omegas as Cascades
- Charge of the Cascade Candidates is determined by the cascade builder
- Adding "BeforeCuts" and "AfterCuts" in the selection class of femtodream (for tracks and cascades only for now) - chaning std::abs() to std::fabs() in the track and cascade selection - adding the Omega selection flag in the producer task to select Omegas as Cascades
…e charge in femtodream
| return false; | ||
| } | ||
| if (nEtaSel > 0 && std::abs(eta) > etaMax) { | ||
| if (nEtaSel > 0 && std::fabs(eta) > etaMax) { |
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.
std::abs is safe in case you wanted to keep it
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.
I approve it for the time being but the following linter recommendations need to be addressed in the next iteration
- the inclusion of
<iostream>, impact compilation time and should not be used in O2Physics - the use of
<TDatabasePDG.h>is quite inefficient regarding memory usage - use constant references for non-modified iterators in loops, that prevent inefficient memory management and access and also accidental inter-task common data modification which is really hard to catch
The rest of the linker recommendations needs to be addressed in a timely manner
And, please, remove all commented code, they reduce readability