[PWGCF] Add Lambda and anti-Lambda spin-correlation analysis - #17837
Draft
Akash-Raj-285 wants to merge 8 commits into
Draft
[PWGCF] Add Lambda and anti-Lambda spin-correlation analysis#17837Akash-Raj-285 wants to merge 8 commits into
Akash-Raj-285 wants to merge 8 commits into
Conversation
|
O2 linter results: ❌ 1 errors, |
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
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.
Summary
This draft PR introduces a PWGCF workflow for studying spin correlations in Lambda–anti-Lambda, Lambda–Lambda, and anti-Lambda–anti-Lambda pairs.
The workflow reconstructs and selects Lambda and anti-Lambda candidates, provides optional Monte Carlo truth and efficiency processing, and produces same-event and mixed-event spin-correlation distributions.
The spin observable is constructed from the proton and antiproton daughter momenta after boosting them into their respective parent hyperon rest frames.
Main components
The workflow contains the following analysis tasks:
LambdaOrAntiLambdaProducerWithSpinLambdaAntiLambdaSelectorLambdaAntiLambdaPairAnalysisLambdaAntiLambdaMcRecoTableProducerLambdaAntiLambdaEfficiencyPlotsLambdaAntiLambdaSelectionCutFlowThe MC-specific processing functions use
PROCESS_SWITCHand are disabled by default, allowing them to be enabled explicitly for MC processing without changing the workflow topology.Same-event pair classification
Same-event pairs are divided into short-range and long-range samples.
A pair is classified as short range when both conditions are satisfied: