Skip to content

Conversation

@zhangbiao-phy
Copy link
Collaborator

@zhangbiao-phy zhangbiao-phy commented Dec 3, 2025

I found the D0 v2 is enhanced a lot when I use the TPC or TPCpos and TPCneg as reference Q vector, the issue is normalization of the Q-vector, I try to fix it by the method show in the first bullet:

  1. Use the original amplitude amplQVec when computing daughter contributions. → Ensures the same normalization used in the Q-vector construction.

Subtract only the prongs that contribute to the selected sub-event:

TPCPos: η > 0
TPCNeg: η < 0
TPCTot: all prongs

Unified the daughter-track calculation into a single helper (getQvecDtracks).

  1. Add the flag to store eta of candidates (for the eta-gap and non-flow study)
  2. refractor the FillThn to make it more flexible and robust

Tagging the flow analyser for comments and questions: @stefanopolitano @wuctlby @Marcellocosti

@github-actions github-actions bot added the pwghf PWG-HF label Dec 3, 2025
@github-actions github-actions bot changed the title correct daughter-track removal from TPC Q-vector in SP method [PWGHF] correct daughter-track removal from TPC Q-vector in SP method Dec 3, 2025
@github-actions
Copy link

github-actions bot commented Dec 3, 2025

O2 linter results: ❌ 0 errors, ⚠️ 0 warnings, 🔕 0 disabled

Comment on lines 451 to 462
if (storeEP) {
values[n++] = cosNPhi;
values[n++] = sinNPhi;
values[n++] = cosDeltaPhi;
}
if (storeMl) {
values[n++] = outputMl[0];
values[n++] = outputMl[1];
}
if (storeCandEta) {
values[n++] = eta;
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is very bug-prone. The positions of elements depend on external switches.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the comment, I see your point. In this implementation the element positions are controlled by the same switches and in the same order as in the axis definition

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but you have to manually check the correct order.

Copy link
Collaborator Author

@zhangbiao-phy zhangbiao-phy Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed, but this is current solution! Maybe I will find more smart way in the next PR

@zhangbiao-phy zhangbiao-phy enabled auto-merge (squash) December 3, 2025 19:49
alibuild
alibuild previously approved these changes Dec 3, 2025
Copy link
Collaborator

@alibuild alibuild left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approving on behalf of @zhangbiao-phy.

Copy link
Collaborator

@alibuild alibuild left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approving on behalf of @zhangbiao-phy.

@zhangbiao-phy zhangbiao-phy merged commit dd3985c into AliceO2Group:master Dec 4, 2025
20 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pwghf PWG-HF

Development

Successfully merging this pull request may close these issues.

3 participants