Repository navigation
Conversation
|
O2 linter results: ❌ 0 errors, |
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
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 PR implements a task that calculates the number of global tracks from the reduced datasets based on configurable track properties and with track-to-collision association. The default values for the global track definition are taken from https://aliceo2group.github.io/analysis-framework/docs/analysis-tools/TrackSelection.html. The common multiplicity estimator does not allow for this.
The task will later be updated to also calculate the multiplicity in azimuthal regions with respect to a ditrack / dielectron candidate. Also, removing the legs from the multiplicity is planned to be implemented in the future.
The multiplicity is estimated separately and made available in the VarManager, such that introducing event-selection cuts can be applied on that value.
Overview planned implementations: