Skip to content

[PWGHF] Add Lc->pK0s channel in polarization task.#15635

Open
XXL-2025 wants to merge 5 commits intoAliceO2Group:masterfrom
XXL-2025:Lcpk0spPolarisation
Open

[PWGHF] Add Lc->pK0s channel in polarization task.#15635
XXL-2025 wants to merge 5 commits intoAliceO2Group:masterfrom
XXL-2025:Lcpk0spPolarisation

Conversation

@XXL-2025
Copy link
Copy Markdown

@XXL-2025 XXL-2025 commented Apr 2, 2026

@github-actions github-actions bot added the pwghf PWG-HF label Apr 2, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

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

@vkucera
Copy link
Copy Markdown
Collaborator

vkucera commented Apr 2, 2026

@XXL-2025 Who are you?

@XXL-2025 XXL-2025 force-pushed the Lcpk0spPolarisation branch from a72b372 to 4c9e4f8 Compare April 2, 2026 17:17
@XXL-2025
Copy link
Copy Markdown
Author

XXL-2025 commented Apr 2, 2026

@vkucera I am a new analyzer from China, and I’m currently learning the analysis from Mattia.

@mfaggin
Copy link
Copy Markdown
Collaborator

mfaggin commented Apr 7, 2026

hi @vkucera, Xianxian is a student working with me. He is trying to implement the Lambdac->pK0s channel in the polarization task in O2Physics to do the analysis.
I asked him to open the PR as a draft on purpose not to trigger any notification to the reviewers because I wanted to check it first, and secondly I'd have introduced Xianxian once the PR would have been released for the review.

@mfaggin
Copy link
Copy Markdown
Collaborator

mfaggin commented Apr 7, 2026

now we do not manage to reopen the PR anymore, is it maybe because you @vkucera should act somehow? Can you please let us know? Thank you

@XXL-2025 XXL-2025 reopened this Apr 7, 2026
@XXL-2025 XXL-2025 force-pushed the Lcpk0spPolarisation branch from 4c9e4f8 to 28c7967 Compare April 7, 2026 07:58
@mfaggin
Copy link
Copy Markdown
Collaborator

mfaggin commented Apr 7, 2026

we understood how to reopen it, I'll review it later

Copy link
Copy Markdown
Collaborator

@mfaggin mfaggin left a comment

Choose a reason for hiding this comment

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

thanks @XXL-2025 for the development. There are some adjustments to be done, please address my comments and test locally your code in both data and MC.

Copy link
Copy Markdown
Collaborator

@mfaggin mfaggin left a comment

Choose a reason for hiding this comment

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

thanks @XXL-2025 for the development. There are some adjustments to be done, please address my comments and test locally your code in both data and MC.

@vkucera
Copy link
Copy Markdown
Collaborator

vkucera commented Apr 8, 2026

Hi @mfaggin @XXL-2025 , thanks for the clarification.
For the sake of transparent collaboration, I think that we should all show our names in our GitHub accounts and we should not accept pull requests from anonymous GitHub accounts.

Copy link
Copy Markdown
Collaborator

@mfaggin mfaggin left a comment

Choose a reason for hiding this comment

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

thanks @XXL-2025 a few more adjustments needed, see the detailed comments. In general:

  • try to reduce as much as possible modifications in pieces of codes that might affect other analyses
  • do not remove comments / add useless new lines etc already present, to reduce entropy

{
/// check process functions
std::array<int, 13> processes = {doprocessDstar, doprocessDstarWithMl, doprocessLcToPKPi, doprocessLcToPKPiWithMl, doprocessDstarMc, doprocessDstarMcWithMl, doprocessLcToPKPiMc, doprocessLcToPKPiMcWithMl, doprocessLcToPKPiBackgroundMcWithMl, doprocessDstarInPbPb, doprocessDstarWithMlInPbPb, doprocessDstarMcInPbPb, doprocessDstarMcWithMlInPbPb};

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

still new line present compared to the original version, please remove it

@XXL-2025
Copy link
Copy Markdown
Author

Thanks a lot for detailed comments.
This is the revised version.

Copy link
Copy Markdown
Collaborator

@mfaggin mfaggin left a comment

Choose a reason for hiding this comment

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

thanks @XXL-2025 , almost there :)
Still a few comments from my side, after implementing them retry also to compile locally and rerun on both data and MC

@mfaggin mfaggin marked this pull request as ready for review April 10, 2026 15:27
@mfaggin
Copy link
Copy Markdown
Collaborator

mfaggin commented Apr 10, 2026

With this PR we want to add the Lambdac->pK0s channel in the polarization task.
The work has been done by Xianxian, who is working with me for this analysis.
@fgrosa since you and Mingze use the same code, I'd ask you to have an independent look. The developments should be basically harmless for you, but better to have a further look from your side.

Thank you in advance

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