[PWGCF] Fix V0V0 processing in femto framework - #17255
Open
ariedel-cern wants to merge 1 commit into
Open
Conversation
|
O2 linter results: ❌ 0 errors, |
ariedel-cern
marked this pull request as ready for review
July 29, 2026 14:46
ariedel-cern
requested review from
alibuild,
dimihayl,
lauraser,
lgraczykCern,
majanik,
prchakra,
shouqiye,
victor-gonzalez and
wrzesaCERN
as code owners
July 29, 2026 14:46
ariedel-cern
enabled auto-merge (squash)
July 29, 2026 21:10
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR addresses two issues:
processLambdapath in the derived-to-derived producer. Following a DF switch, the track table index was not reinitialized, leading to a mismatch between V0 entries and their daughter-track indices in the output.Lambda–AntiLambdaprocessing in thev0v0task. The fix required introducing and renaming several configurables to properly separate the processing paths.