[PWGLF] EMCal in sigma0 analysis#15577
Merged
romainschotter merged 5 commits intoAliceO2Group:masterfrom Mar 30, 2026
Merged
Conversation
Please consider the following formatting changes to AliceO2Group#15577
Collaborator
|
Error while checking build/O2Physics/o2 for e2faca9 at 2026-03-30 16:15: Full log here. |
romainschotter
approved these changes
Mar 30, 2026
Collaborator
|
@gianniliveraro @romainschotter There are missing includes. Don't ignore them. |
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 mainly includes the option to reconstruct and analyze sigma0 candidates using EMCal information (provided by the emcalCorrectionTask). For this, a set of dedicated process functions / tables / histograms / etc were added/modified to process both DATA and MC. The option to use only PCM photons remains untouched.
These changes are for a simple feasibility study. Hence, the code should be further improved in a future PR.
@Oussama3030 and @ddobrigk for your information :)