-
Notifications
You must be signed in to change notification settings - Fork 613
[PWGCF] Adding selection on V0 rapidity in cf correlation #12210
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
Merged
victor-gonzalez
merged 4 commits into
AliceO2Group:master
from
stefanopolitano:dev_spolitan_oo_vzero
Jul 25, 2025
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
aefe1c3
[PWGCF] Adding selection on V0 rapidity in cf correlation function
stefanopolitano 5b29348
Please consider the following formatting changes
alibuild f46050f
Merge pull request #21 from alibuild/alibot-cleanup-12210
stefanopolitano 0b51095
[PWGCF] Implementing Victor comments
stefanopolitano File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Hi @stefanopolitano, I think this line is buggy, because for unidentified types it returns -999, but your
absmakes it always larger than your defaultcfgV0RapidityMax, which is 0.8 by default. This rejects all D0s, for example. Perhaps the default should be negative?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.
Hi @jaelpark! Indeed, this cut was not ment for D0s since the rapidity cut is typically applied at the skimming/task level, but only for LF V0s. I can change the default value to avoid misunderstanding, although one can always set the configuration value to
0to switch the selection offThere 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.
Thanks. I think we shouldn't let new users of the D0 code be confused why everything is rejected. Another option is to return two values (
std::tuple<float, bool>) fromgetV0Rapidityto indicate with a bool whether the selection applies.