Decay files of leptonic decay of HNLs produced from Bd and Bc decay

The decay files describe the following processes;

• Bc+ -> mu+ (N -> mu+ mu- anti-nu_mu)
• Bc+ -> mu+ (N -> mu+ e- anti-nu_e)
• Bc+ -> mu+ (N -> anti-nu_mu e+ e-)
• B+ -> mu+ (N -> mu+ mu- anti-nu_mu)
• B+ -> mu+ (N -> mu+ e- anti-nu_e)
• B+ -> mu+ (N -> anti-nu_mu e+ e-)
• B+ -> mu+ X0 (N -> mu+ mu- anti-nu_mu)
• B+ -> mu+ X0 (N -> mu+ e- anti-nu_e)
• B+ -> mu+ X0 (N -> anti-nu_mu e+ e-)
• B0 -> mu+ X- (N -> mu+ mu- anti-nu_mu)
• B0 -> mu+ X- (N -> mu+ e- anti-nu_e)
• B0 -> mu+ X- (N -> anti-nu_mu e+ e-)

for HNLs with 2 GeV and 4 GeV. N represents HNLs. X is a hadron (pi, rho, D and D*). HNLs produced from Bc decay have mass 2, 4 and 5.5 GeV, HNL produced from leptonic B+ decay have mass 2, 4 and 5 GeV. HNLs produced from semileptonic B+ or B0 decay have mass 1.6, 2, 3 and 4 GeV.

changed title from Decay files of leptonic decay of HNLs produced from Bd decay to Decay files of leptonic decay of HNLs produced from Bd and Bc decay

changed the description

requested review from @emmuhamm

added 1 commit

• 2d1b6c9c - Added dec files for HNLs produced from Bc, Bu (semileptonic and leptonic) and...

Compare with previous version

changed the description

requested review from @lgiambas

I'm seeing a lot of warnings in the decfile CI test, specifically those that are like

testing dkfiles/Bd_MuXMajoranaNeutrino2EENu,m=3000MeV,t=100ps,SS,DecProdCut.dec
Checking track flag.........................................WARNING
Track flag not compliant. Should be: 3. Please check.

Can you take a look at the ci test result for the check-decfiles job and fix all the ones that are specifically talking about the flags?

There are other warnings that I think you can safely ignore:

Ones that check the descriptors,

Checking descriptor.........................................WARNING
636Descriptor not matched. Please check the old one:
637[B0 -> (Higgs0 -> anti-nu_mu e- e+) mu+ X]cc
638And the one built by the parser: 
639[B0 -> D- (H_10 -> anti-nu_mu e- e+) mu+]cc

and the checking the funky bits,

Checking the extra and user for duplicity and funky stuff...The decfile: Bu_MuMajoranaNeutrino2MuMuNu,m=2000MeV,t=100ps,SS,DecProdCut:12513080 uses this extra flag, but the decay seems different. Please check and use a unique extra flag.
1231The decfile: Bu_MuMajoranaNeutrino2MuENu,m=2000MeV,t=100ps,SS,DecProdCut:12513081 uses this extra flag, but the decay seems different. Please check and use a unique extra flag.
1232The decfile: Bu_MuMajoranaNeutrino2MuMuNu,m=4000MeV,t=100ps,SS,DecProdCut:12513083 uses this extra flag, but the decay seems different. Please check and use a unique extra flag.
1233The decfile: Bu_MuMajoranaNeutrino2MuENu,m=4000MeV,t=100ps,SS,DecProdCut:12513084 uses this extra flag, but the decay seems different. Please check and use a unique extra flag.
1234DONE

added 1 commit

• 3aeb6475 - Changed neutral or track flags of modified files to avoid warnings from the...

Compare with previous version

Thank you for your comment. I have changed the track and neutral flags of files that gave warnings. I think you should find the updated files no longer produce these warnings.

Looks good to me, I'll go ahead and approve it

FYI I'm still seeing

Checking neutrals flag......................................WARNING
1926Neutrals flag not compliant. Should be 0. Please check.

In some of the decfile tests in check-decfiles test. However, this particular one came from testing dkfiles/Bu_MuXMajoranaNeutrino2EENu,m=2000MeV,t=100ps,SS,DecProdCut.dec which is not in this merge request, so you should be fine.

cc @kreps this is a behaviour which you might find interesting

approved this merge request

merged

mentioned in commit eb688f58

picked the changes into the branch cherry-pick-eb688f58 with commit 0691f112

mentioned in commit 0691f112

mentioned in merge request !1444 (merged)

mentioned in issue lhcb-simulation/mc-requests#88 (closed)