Skip to content

[PWGDQ] Use RCT Flags in tableReader_withAssoc and dqEfficiency_withAssoc - #18468

Open
axti98 wants to merge 2 commits into
AliceO2Group:masterfrom
axti98:RCTFlagsInReader
Open

axti98 wants to merge 2 commits into
AliceO2Group:masterfrom
axti98:RCTFlagsInReader

Conversation

@axti98

@axti98 axti98 commented Oct 26, 2026

Copy link
Copy Markdown
Collaborator

For now, the run condition table (RCT) flags could only be set during skimming. To avoid new skimmings, fetch RCT information from CCDB per run and do the rejection for the skimmed tasks.

@github-actions github-actions Bot added the pwgdq label Oct 26, 2026
@github-actions

Copy link
Copy Markdown

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

@axti98
axti98 marked this pull request as ready for review October 27, 2026 17:54
@axti98

axti98 commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator Author

@mguilbau @XiaozhiBai @shreyasiacharya @glegras @iarsene

I have tested now and it should work as intended. I have just one remark which me might need to discuss. In MC, the reconstructed collisions are rejected if a corresponding flag is set, but the MC Truth collision is kept. This is the same behaviour as in the TableMaker(MC). This has for itself no problems, but silently is entering the definition of efficiencies.

For now, we take bad detector conditions with the RCT flag as "Efficiency Loss", the true collision stays, but the reconstructed one is removed. The question is whether this definition is intended like this or if also the MC Collisions should be handled.

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.

1 participant