PWGHF: rename config of OmegaC->Omega in OmegaC NoDecay #1871
+8
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mpuccio and I realised that
does not work, since in PYTHIA the OmegaC is always decayed to diquarks/quarks that then hadronise later on, so we cannot select the decays with a specific hadron in the final state. To avoid misunderstanding I rename the relative config, which produces events with OmegaC that do not decay.
This can be used to produce pregenerated pools of events with undecayed OmegaC baryons, that can be decayed later on with GEANT using an external generator (the same pool can be used for several productions requiring different forced decays of OmegaC), provided this fix in
GENAT4_VMC
vmc-project/geant4_vmc#70.