[PWGDQ] Adding functionality for event mixing across TFs#16528
Merged
Conversation
iarsene
requested review from
alibuild,
lucamicheletti93 and
mcoquet642
as code owners
|
O2 linter results: ❌ 380 errors, |
github-actions
Bot
changed the title
[PWGDQ] Please consider the following formatting changes to AliceO2Group#16528
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is implemented so far just for the dielectron channel, in the table-reader-with-assoc. The event mixing categories are created in the same way as for the usual mixing (within a single TF), but they are configured directly in the same-event-pairing task.
In this mixing, the candidate electrons are temporarily stored in event pools which are permanent (data members of the task) and included in the mixing using a rolling buffer of configurable depth. The important aspect is that in the case when mixing is done with very many categories or the signal is very rare, and the pools cannot be filled during a single TF, this method will allow using all the TFs in the job, so all pools can get enough events.