[PWGLF,Trigger] [Event Filtering] adding trigger condition for lambdalambda #10885
Conversation
jikim1290
requested review from
ChiaraDeMartin95,
alibuild,
ercolessi,
lietava and
mpuccio
as code owners
github-actions
bot
changed the title
mpuccio
left a comment
mpuccio
left a comment
There was a problem hiding this comment.
Hi Junlee, thanks a lot! I think that with the current implementation you are selecting only LL and not antiL antiL pairs. Can you have a look?
| if (v00.globalIndex() <= v01.globalIndex()) { | ||
| continue; | ||
| } | ||
|
|
There was a problem hiding this comment.
Before building the second V0, can you also check that there is no overlapping index for the daughters of the two V0s? I see that it is done later, but in general we should do simple checks as early as possible to avoid computing vertices that need to be discarded.
There was a problem hiding this comment.
The number of lambdas in pp is not that high so I think it would be not that bigger usage. By the way, can you please teach me the logic for that? I can try to implement it but it look needing 2 independent loops for v0.
There was a problem hiding this comment.
Ah, yes it is v0 cadidate loop that including many more than only lambda..
| } | ||
| int Tag = 0; | ||
| if (cfgPIDPi > std::fabs(negTrack0.tpcNSigmaPi()) && cfgPIDPr > std::fabs(posTrack0.tpcNSigmaPr())) { | ||
| if (cfgLambdaMassWindow > std::fabs(mStraHelper.v0.massLambda - o2::constants::physics::MassLambda0) || cfgCompV0Rej < std::fabs(mStraHelper.v0.massK0Short - o2::constants::physics::MassLambda0)) { |
There was a problem hiding this comment.
I think that for the competing mass hypothesis you need to have a K0s in the second condition
| continue; | ||
| } | ||
| int Tag = 0; | ||
| if (cfgPIDPi > std::fabs(negTrack0.tpcNSigmaPi()) && cfgPIDPr > std::fabs(posTrack0.tpcNSigmaPr())) { |
There was a problem hiding this comment.
If you do like this, an anti-lambda might be skipped here. You should consider also the antilambda hypothesis
There was a problem hiding this comment.
From L644 to L655, I checked the candidate could be lambda or antilambda.
If both hypotheses work, Tag would be two and if none of two hypotheses work, Tag would be zero.
I accept the case when only one hypothesis is correct, which means that I select either only lambda or anti-lambda
It is intended to have lambda-lambda and antilambda-antilambda pair to see the signal and lambda-antilambda pair for cross check.
|
@mpuccio I have implemented preselection only for lambda so two loop after the selection would be not to heavy as the number of lambda (after selection) in pp would be not that large. |
Please consider the following formatting changes to AliceO2Group#10885
Please consider the following formatting changes to AliceO2Group#10885
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
…lambda (AliceO2Group#10885) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
3 participants
adding trigger condition for lambdalambda