[ALICE3] Added Multiplicity estimator task for ALICE3 - #17540
Conversation
|
O2 linter results: ❌ 58 errors, |
Please consider the following formatting changes to AliceO2Group#17540
| trackParCov.getSigma1Pt2()); | ||
| tableMcTrackLabels(trackParCov.mcLabel, 0); | ||
| tableTracksExtraA3(trackParCov.nSiliconHits, trackParCov.nTPCHits, trackParCov.trackType); | ||
| tableTracksExtraA3(trackParCov.nSiliconHits, trackParCov.nTPCHits, trackParCov.trackType, true); |
There was a problem hiding this comment.
shouldn't it be only if the track is a contributor?
There was a problem hiding this comment.
Yes, I think I misunderstood something earlier. I have implemented it now that every track that contributed has a flag now which is checked in the table filling
|
|
||
| auto charge = 0.; | ||
| auto* p = pdg->GetParticle(mcParticle.pdgCode()); | ||
| if (p != nullptr) { |
There was a problem hiding this comment.
for counting particles we can use https://github.com/AliceO2Group/O2Physics/blob/master/PWGLF/Utils/inelGt.h#L96
There was a problem hiding this comment.
I count it in several eta intervals, I would not use this function since then we have to loop again for each eta interval over all tracks which is quite inefficient?
| multMC(numMCParticles, numMCParticlesEta25, numMCParticlesEta125, numMCParticlesEta09); | ||
| } | ||
|
|
||
| void processDummy(const aod::Collision&) |
There was a problem hiding this comment.
why do you need the dummy?
There was a problem hiding this comment.
Its sometimes more convenient on hyperloop to have a dummy process so you don't need to remove the task all the time
|
Error while checking build/O2Physics/code-check for 2427e80 at 2026-08-21 15:01: Full log here. |
…nto Alice3MultDev Merge auto-format suggestion
|
Error while checking build/O2Physics/staging for a8c7c4f at 2026-08-24 12:48: Full log here. |
|
Error while checking build/O2Physics/code-check for 5cdbb84 at 2026-08-24 17:00: Full log here. |
Added basic multiplicity estimator task in preparation for PbPb studies and multiplicity dependent studies. Currently, two estimator types are implemented:
Necessary changes in the TrackingTranslator because of data model change as well as in OTF Tracker