Skip to content

[PWGCF] Femto: add Lc support to the femto framework - #17424

Open
IgorPtak wants to merge 11 commits into
AliceO2Group:masterfrom
IgorPtak:femto-lc
Open

[PWGCF] Femto: add Lc support to the femto framework#17424
IgorPtak wants to merge 11 commits into
AliceO2Group:masterfrom
IgorPtak:femto-lc

Conversation

@IgorPtak

Copy link
Copy Markdown
Contributor

Adds Lc baryons as a new particle species to the unified femto framework, enabling
Lc-hadron femtoscopic correlations.

Data model - four new tables:

  • FLcs - kinematics, mass of the accepted hypothesis and the three daughter indices
  • FLcMasks - selection bitmask
  • FLcExtras - QA/debug: mass of the competing hypothesis, three-prong topological
    variables, BDT scores and the PWGHF selection flags
  • FLcLabels - MC labels

Core: charmHadronBuilder.h and charmHadronHistManager.h extended to the
three-prong topology, so both species share the same builder and histogram manager.
Lc candidates are taken from PWGHF (HfCand3Prong), with the acceptance applied as
a rapidity cut via HfHelper. Unlike D0, the sign of the stored signed pT is the
physical baryon charge, taken from the charge of the first prong - the PWGHF flags
only tell which mass assignment passed. Prongs are stored remapped onto the accepted
hypothesis, so Prong0Dau always points at the proton.

The naming of everything shared by the family was generalised from D0 to charm
hadron (ConfD0Filters -> ConfCharmHadronFilters, fillD0s -> fillCharmHadrons,
and so on). Species-level names (D0Bits, D0Selection1) are unchanged.

Tasks: the two D0 workflows now cover the whole family.

  • femto-charm-hadron-qa (was femto-d0-qa) - QA for D0 and Lc candidates
    and their daughters
  • femto-pair-track-charm-hadron (was femto-pair-track-d0) - D0-hadron and
    Lc-hadron correlations, same and mixed event

JSON prefixes changed accordingly: D0Filters -> CharmHadronFilters,
D0Tables -> CharmHadronTables.

Pairs: TrackLcPairCleaner and ClosePairRejectionTrackLc are new.

MC: Lc candidates have no direct MC label, so the three prongs are
matched to a generated Lc -> p K pi decay with RecoDecay::getMatchedMCRec.

Mass hypotheses: an Lc candidate can pass both the pKpi and the piKp hypothesis.
One row is stored per accepted hypothesis, so such a candidate appears twice, each
row with its own mass and prong assignment. CharmHadronFilters.rejectAmbiguousHypothesis allows dropping them entirely.

@github-actions

Copy link
Copy Markdown

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

Please consider the following formatting changes to AliceO2Group#17424
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants