Skip to content

Conversation

@yashpatley
Copy link
Contributor

  1. Added track table to fix previous error of table size mismatch
  2. Added v0 flow

1. Added track table to fix previous error of table size mismatch
2. Added v0 flow
@github-actions
Copy link

github-actions bot commented Jan 17, 2026

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

@github-actions github-actions bot changed the title [PWGCF]: Update flowEventPlane.cxx [PWGCF] Update flowEventPlane.cxx Jan 17, 2026
Removed mass calculation for Lambda and AntiLambda.
Copy link
Collaborator

@victor-gonzalez victor-gonzalez left a comment

Choose a reason for hiding this comment

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

I guess there are no plans of using stored derived data
Why then recreate and store information that is already available in the Tracks tabel?

@yashpatley
Copy link
Contributor Author

yashpatley commented Jan 19, 2026

Dear Victor,
This is because I added the pion, kaon, proton flags in the table earlier. But there was a size mismatch issue when I was joining it with the track table. This was because of the Collision selection condition in the process. I wanted the identified tags so I can use them to reconstruct resonance later in another workflow. The reason I modified it this way is because when I composed the wagon on HL for large dataset it showed memory warning. And it was because of the track combinations. So with the identification and a partition I was able to reduce the memory consumption. That's why this way. Also, I discussed with Debojit and we plan to use derived data in future from the large data set for tracks and collisions with zdc flow vectors. Let me know if changes are required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants