[mhemmer-cern]

…ns in emcalCorrectionTask

emcTmMonitor:

• Replace the simple event selection (kINT7 / kTVXinEMC alias and a z-vertex cut) by an EMCal event selection with the standard cuts of the event selection task, configurable in the eventCuts group:
  • sel8 (default on) and |z_vtx| (default 10 cm)
  • EMCal in the readout (Run 2: kINT7, Run 3: kTVXinEMC)
  • one switch per evsel flag: TF/ITS ROF borders, same-bunch pile-up, z_vtx FT0 vs PV, ITS-TPC / TOF-matched vertex, collisions in time range / ROF, high-multiplicity collision in previous ROF, ITS layers
  • track and FT0C occupancy ranges, applicable at the same time
  • RCT flags via RCTFlagsChecker (label configurable, default CBT_calo)
  • centrality or multiplicity range with a configurable estimator (FT0C, FT0M, FT0A centrality; FT0C, FT0A, FT0M, NTracksPV multiplicity)
• Apply vetoBCID / selectBCID, which were parsed but never used.
• Add event QA: cut flow histogram, occupancy and centrality/multiplicity before and after the selection, BC ID of the selected events.
• doEventSel and vertexCut are kept as deprecated aliases of eventCuts.requireEmcalReadout and eventCuts.zVertexMax.
• The collision table now joins CentFT0Cs, CentFT0Ms, CentFT0As, FT0Mults and PVMults: the centrality and multiplicity tables have to be produced in the workflow.

emcalCorrectionTask:

• Move trackMinPt into the new trackmatching configurable group (now trackmatching.trackMinPt).
• Add trackmatching.useAllTracks to use all tracks instead of only global tracks for the track matching. To give a bit more context here, in the current PbPb data and MC reconstruction we did not prune the unused TPC-only tracks. Track matching studies show that we can match a lot of these tracks to the EMCal. To enable further studies it would be good to get this configurable into the code.

[github-actions]

O2 linter results: ❌ 0 errors, ⚠️ 0 warnings, 🔕 19 disabled

[fjonasALICE]

looks all reasonable to me