Gauss merge requestshttps://gitlab.cern.ch/lhcb/Gauss/-/merge_requests2024-03-26T14:34:38+01:00https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/1045No Acceptance Cuts for daughters of Long Lived particles2024-03-26T14:34:38+01:00Andrea MerliNo Acceptance Cuts for daughters of Long Lived particlesOnly daughters of $\Omega^-$, $\Xi^-$, $\Xi^0$, $\Lambda^0$ and $K_S$ are removed from the acceptance cut of standard tools [DaughtersInLHCb.cpp#L95](https://gitlab.cern.ch/lhcb/Gauss/-/blob/Sim10/Gen/GenCuts/src/DaughtersInLHCb.cpp?ref_...Only daughters of $\Omega^-$, $\Xi^-$, $\Xi^0$, $\Lambda^0$ and $K_S$ are removed from the acceptance cut of standard tools [DaughtersInLHCb.cpp#L95](https://gitlab.cern.ch/lhcb/Gauss/-/blob/Sim10/Gen/GenCuts/src/DaughtersInLHCb.cpp?ref_type=heads#L95). Acceptance cuts are wrongly applied to daughters of $\Sigma^+$, $\Sigma^-$, long lived user defined particles (e.g. [Bd_MuPiMajoranaNeutrino2MuPi,m=3000MeV,t=100ps,DecProdCut.dec](https://gitlab.cern.ch/lhcb-datapkg/Gen/DecFiles/-/blob/v30r102/dkfiles/Bd_MuPiMajoranaNeutrino2MuPi,m=3000MeV,t=100ps,DecProdCut.dec), [Bd_MuXMajoranaNeutrino2EENu,m=4000MeV,t=100ps,SS,DecProdCut.dec](https://gitlab.cern.ch/lhcb-datapkg/Gen/DecFiles/-/blob/v30r102/dkfiles/Bd_MuXMajoranaNeutrino2EENu,m=4000MeV,t=100ps,SS,DecProdCut.dec)) or resonances produced in long lived user defined particles (e.g. [Bd_MuXMajoranaNeutrino2MuX,m=1600MeV,t=1000ps,SS,DecProdCut.dec](https://gitlab.cern.ch/lhcb-datapkg/Gen/DecFiles/-/blob/v30r102/dkfiles/Bd_MuXMajoranaNeutrino2MuX,m=1600MeV,t=1000ps,SS,DecProdCut.dec)). Here I propose a much robust way to identify the daughters of long lived particles that does not rely on PDG ID. For the time being, the changes have been implemented only in DaughtersInLHCb. If they are accepted, I will implement them also in all the other tools that use the old buggy logic to exclude long lived particle daughters. This merge request has to be ported also to Sim09.Andrea MerliAndrea Merlihttps://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/1003Draft: Remove particles already in G4 10.7.32024-03-28T00:22:41+01:00Gloria CortiDraft: Remove particles already in G4 10.7.3Remove particles that are now defined in G4 10.7 with the same PDG ID but different names.
It replace the first commits of lhcb/Gauss!974 that diverged from original purpose
cc: @veltri, @dpopov, @witoldp, @clemenci
This needs to be ...Remove particles that are now defined in G4 10.7 with the same PDG ID but different names.
It replace the first commits of lhcb/Gauss!974 that diverged from original purpose
cc: @veltri, @dpopov, @witoldp, @clemenci
This needs to be cherry-picked to `master` as it will need to propagate to `Sim11`, cc: @mimazurehttps://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/944Fix Inclusive Userhook bug and configuration2024-03-29T00:06:14+01:00Tom HadavizadehFix Inclusive Userhook bug and configurationThis MR addresses two issues with the inclusive b-quark Userhook implementations for Pythia.
- The pT scale of the veto applied during the event evolution was being used before it was initialised. I've added more checks to prevent this ...This MR addresses two issues with the inclusive b-quark Userhook implementations for Pythia.
- The pT scale of the veto applied during the event evolution was being used before it was initialised. I've added more checks to prevent this happening.
- When used with most generation tools (e.g. SignalPlain or SignalRepeatedHadronisation) using the Userhooks will mean the pileup events are also produced with b-quarks in them. I've rewritten the python steering script to overwrite the chosen generation tool and force the use of 'Special', allowing separate Pythia instances for the signal and pile up. The normal 'DaughtersinLHCb' generator level cuts don't work with the Special tool so I've had to use the 'BcDaughtersinLHCb' tool and change the particle ID to different hadrons according to the requested EventType.
- The QMtest has been updated to use the new options fileSim10/2024.02 (Gauss v56r8)