Skip to content

Add a decay config that lets the EventDecayer decay charm baryons - #2518

Open
sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:eventdecayer-charmbaryon-cfg
Open

sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:eventdecayer-charmbaryon-cfg

Conversation

@sawenzel

Copy link
Copy Markdown
Contributor

This adds a small decay config, eventdecayer_charmbaryon.cfg, that switches on the decays of Ξc⁰, Ξc⁺ and Ωc⁰ for the new decay step in event generation (EventDecayer, AliceO2Group/AliceO2#15995).

base.cfg keeps these charm baryons stable, because Geant4 hands them to the external decayer one at a time. With the decay step they are decayed before transport, and the full decay chain, including intermediate resonances such as Ξ(1530)⁰, K*⁰ and φ, is kept in the MC truth. The forced channels of force_hadronic_charmbaryon*.cfg are used unchanged.

Usage in a request:

DecayerPythia8.config[1]=${O2DPG_MC_CONFIG_ROOT}/MC/config/PWGHF/pythia8/decayer/force_hadronic_charmbaryon.cfg;EventDecayer.enable=true;EventDecayer.config[2]=${O2DPG_MC_CONFIG_ROOT}/MC/config/PWGHF/pythia8/decayer/eventdecayer_charmbaryon.cfg

Note that the file has no effect unless EventDecayer.enable=true is set, so nothing changes for existing requests.

https://its.cern.ch/jira/browse/O2-5903
https://its.cern.ch/jira/browse/O2-7108

Assisted by Claude Code.

This commit adds eventdecayer_charmbaryon.cfg, which switches on the decays of Xi_c0, Xi_c+ and Omega_c0 for the EventDecayer.

- base.cfg keeps these charm baryons stable, because Geant4 hands them to the external decayer one at a time.
- The EventDecayer decays them before transport and keeps the full decay chain in the MC truth.

Usage: -confKey 'DecayerPythia8.config[1]=${O2DPG_MC_CONFIG_ROOT}/MC/config/PWGHF/pythia8/decayer/force_hadronic_charmbaryon.cfg;EventDecayer.enable=true;EventDecayer.config[2]=${O2DPG_MC_CONFIG_ROOT}/MC/config/PWGHF/pythia8/decayer/eventdecayer_charmbaryon.cfg'

AliceO2Group/AliceO2#15995
https://its.cern.ch/jira/browse/O2-5903

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sawenzel
sawenzel requested a review from a team as a code owner October 22, 2026 19:19
@github-actions

Copy link
Copy Markdown

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant