[PWGJE] Add MC mixing and adjusting task for use on Hyperloop#12670
Conversation
jkinner2
commented
Aug 21, 2025
jkinner2
commented
- added MC true mixing in the same way as reconstructed data
- split producer task to own file (to allow subwagons with different configurations on Hyperloop)
- added internal multiplicity estimate based on the number of JetTracks
- extended invariant mass/correlation to eta meson
- adjusted an issue in the efficiency process regarding bias towards selected tracks
save_testieTestThingie_deleteCommitLater save_itFinallyCompiled_deleteCommitLater addMcMixing_addEta_generalImprovements
|
O2 linter results: ❌ 1 errors, |
jkinner2
requested review from
alibuild,
fjonasALICE,
maoyx,
mfasDa,
mhemmer-cern and
nzardosh
as code owners
fjonasALICE
left a comment
fjonasALICE
left a comment
There was a problem hiding this comment.
It is too much to look through everything, but @nzardosh since this does not touch any other task, we can approve without fear of breaking?
| } | ||
| PROCESS_SWITCH(PhotonChargedTriggerProducer, processRecoPipmTPC, "process pipm (TPC) table (reconstructed)", false); | ||
|
|
||
| void processRecoPhotonPCM(soa::Join<aod::JetCollisions, aod::JCollisionPIs>::iterator const& collision, aod::Collisions const&, |
There was a problem hiding this comment.
why do you need aod::Collisions const& here?
There was a problem hiding this comment.
The index of aod::Collisions is needed to match the photons to a JetCollision, since aod::V0PhotonsKF from the PCM task does not have an index to aod::JetCollisions
There was a problem hiding this comment.
but you use collision.collisionId(). I think since this is a number that is stored in JCollisions, then there is no need for aod::Collisions to be in the subscription. You could try this locally and see
There was a problem hiding this comment.
When trying to compile with aod::JetCollision const& collision instead of soa::Join<aod::JetCollisions, aod::JCollisionPIs>::iterator const& collision in the process function, I get a compilation error: 'has no member named 'collisionId''. So I would conclude the PIs table is necessary (I assume the globalIndex of aod::JetCollisions should not be used when the index of aod::Collisions is technically needed)
There was a problem hiding this comment.
You still need aod::JCollisionPIs because thats where the Id colum is stored. However the aod::Collisions table is the one you probably dont need to subscribe to
There was a problem hiding this comment.
Yes, sorry. I misunderstood. I have pushed the change
4 participants
