[PWGLF] Add new task: PWGLF/TableProducer/Nuspex/deuteronInTriggeredEvents#16128
Draft
Cristian-Moscatelli wants to merge 4 commits intoAliceO2Group:masterfrom
Draft
[PWGLF] Add new task: PWGLF/TableProducer/Nuspex/deuteronInTriggeredEvents#16128Cristian-Moscatelli wants to merge 4 commits intoAliceO2Group:masterfrom
Cristian-Moscatelli wants to merge 4 commits intoAliceO2Group:masterfrom
Conversation
github-actions
Bot
changed the title
|
O2 linter results: ❌ 2 errors, |
Collaborator
|
Why is this not in PWGJE? |
Contributor
Author
Good afternoon Vit. Thanks for your reply. I decided to put the task in PWGLF/TableProducer/Nuspex since I modify the task nucleiSpectra.cxx, which is in the same directory. What do you think? |
vkucera
reviewed
May 8, 2026
Comment on lines
+31
to
+33
| #include "PWGJE/Core/JetBkgSubUtils.h" | ||
| #include "PWGJE/Core/JetUtilities.h" | ||
| #include "PWGLF/DataModel/LFSlimNucleiTables.h" |
Collaborator
There was a problem hiding this comment.
Suggested change
| #include "PWGJE/Core/JetBkgSubUtils.h" | |
| #include "PWGJE/Core/JetUtilities.h" | |
| #include "PWGLF/DataModel/LFSlimNucleiTables.h" | |
| #include "PWGLF/DataModel/LFSlimNucleiTables.h" | |
| // | |
| #include "PWGJE/Core/JetBkgSubUtils.h" | |
| #include "PWGJE/Core/JetUtilities.h" |
Comment on lines
+50
to
+61
| #include "CCDB/BasicCCDBManager.h" | ||
| #include "DataFormatsParameters/GRPMagField.h" | ||
| #include "DataFormatsParameters/GRPObject.h" | ||
| #include "DetectorsBase/GeometryManager.h" | ||
| #include "DetectorsBase/Propagator.h" | ||
| #include "Framework/ASoAHelpers.h" | ||
| #include "Framework/AnalysisDataModel.h" | ||
| #include "Framework/AnalysisTask.h" | ||
| #include "Framework/HistogramRegistry.h" | ||
| #include "Framework/runDataProcessing.h" | ||
| #include "MathUtils/BetheBlochAleph.h" | ||
| #include "ReconstructionDataFormats/Track.h" |
Comment on lines
+85
to
+88
| struct NucleusCandidate { | ||
| int globalIndex; | ||
| int collTrackIndex; | ||
| float pt; |
Collaborator
There was a problem hiding this comment.
All members are uninitialised.
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.
I created a new task, named deuteronInTriggeredEvents.cxx (PWGLF/TableProducer/Nuspex), to study the (anti-)deuteron pT spectrum in jet-triggered pp collisions. The task is based on nucleiSpectra.cxx (same directory), but provides further selections for events. The analysis flow is the following:
Regarding the processData, the event selection is performed using the skimmed dataset. Specifically, the trigger list used are fChJetLowPt and fChJetHighPt. Apart from this, this part is analogous to nucleiSpectra.cxx.
As for the processMC, the event selection is applied by checking if the event "contains" one valid jet. The same jet definition used in the skimming procedure is adopted:
These event selections are applied to the reconstructed events, and (anti-)deuteron candidate selection follows the same strategy as in nucleiSpectra.cxx. In addition, a dedicated table has been introduced to store MC generated events containing at least one valid jet. This is intended for normalization of the final spectra to the number of jet-triggered events.
This task can also provide a MB analysis, as the jet-triggered event selection is configurable and can be disabled. Furthermore, the analysis can be extended to (anti-)p, (anti-)t, (anti-)He-3 and (anti-)He-4.
I would appreciate any feedback or suggestions. Thanks in advance.