B2OC: changes to reduce rates and updates of BDT

Several attempts are taken to reduce rates for most baryon lines, including:

• add bachelor builders with tighter PID cuts (e.g. make_tightpid_bachelor_kaons)
• add charm builders with tighter cuts (e.g. make_tight_lc_to_pkpi)
• apply cuts on final state tracks in some line builders

Some updates with BDT are made:

• add a new b2chhh BDT which also aims for reducing rates
• add an option for b_to_dh_bdt_filter to make it also usable for B->D* h, D*h->D gamma(pi0) decays
• modify names for BDT xml files accordingly, based on ParamFiles!27

Should be tested with ParamFiles!27

mentioned in merge request lhcb-datapkg/ParamFiles!27 (merged)

@shunan Hi, there is some failure in pipelines, can you solve that before testing?

assigned to @msaur

added hlt2 ~21940 labels

added ci-test-triggered label

• [2020-07-14 17:04] Validation started with lhcb-master-mr#1082
• [2020-07-16 09:55] Validation started with lhcb-master-mr#1090
• [2020-07-16 10:16] Validation started with lhcb-master-mr#1090
• [2020-07-16 10:39] Validation started with lhcb-master-mr#1090
• [2020-07-17 00:15] Validation started with lhcb-gaudi-head-py3#418
• [2020-07-18 00:14] Validation started with lhcb-gaudi-head-py3#419
• [2020-07-19 00:14] Validation started with lhcb-gaudi-head-py3#420
• [2020-07-20 09:55] Validation started with lhcb-gaudi-head-py3#421

@msaur @shunan let me attach here the snapshot of a discussion I had with Rosen about this failure on docs as you will see Rosen told us we can ignore this from our side

fingers crossed for the ci-test

@abertoli Thanks, now it is clear.

sorry @msaur (cc @shunan) myself and Shunan would like to cross check something with you

if you test/run this branch without using at the same time:

lhcb-datapkg/ParamFiles!27 (merged)

it will fail for sure because we have changed some file names in ParamFiles

this "joint" test of the b2oc_upgrade Moore branch and of the b2oc-abertoli-importxml ParamFiles branch was requested/suggested/proposed by Alex

in the description part at the top there is also this line:

modify names for BDT xml files accordingly, based on ParamFiles!27

but as myself and Shunan are not super-experts can we cross check with you that you are indeed performing this "simultaneous" test of both ?

unfortunately this came to our minds only now ...

changed the description

@abertoli @shunan I am also not an expert... Surely both MRs should be tested simultaneously, error on my side I haven't realised that from the description yesterday. In future could be helpful (to make shifter's life easier, thanks) to highlight related MRs in the description like "To be tested/merged together with XYZ" or "Should be tested with XYZ and ZYX." I will run new ci tests including xml MR after the nightlies will finish.

really sorry for this @msaur (cc @shunan)

next time we will pay more attention

many thanks for running new ci tests !

/ci-test --merge ParamFiles!27

For some reason tests hasn't fired up. Running again.

/ci-test --merge lhcb-datapkg/ParamFiles!27 (merged)

added 1 deleted label

mentioned in issue #198 (closed)

assigned to @abrearod and unassigned @msaur

@abrearod this MR was incorrectly labelled ~"lhcb-gaudi-head-py3". I've relabelled as lhcb-head. If this MR looks good tonight, along with the associated lhcb-datapkg/ParamFiles!27 (merged), I'd say we're ready to merge.

added lhcb-head label and removed ci-test-triggered + 1 deleted label

many thanks for your patience and support @apearce

• [2020-07-21 00:38] Validation started with lhcb-head#2658
• [2020-07-22 00:23] Validation started with lhcb-head#2659
• [2020-07-23 00:17] Validation started with lhcb-head#2660
• [2020-07-24 01:58] Validation started with lhcb-head#2661
• [2020-07-24 02:18] Validation started with lhcb-head#2661
• [2020-07-24 02:42] Validation started with lhcb-head#2661
• [2020-07-24 07:51] Validation started with lhcb-head#2661
• [2020-07-24 08:21] Validation started with lhcb-head#2661

approved this merge request

assigned to @jonrob and unassigned @abrearod

resolved all threads

merged

mentioned in commit 3c95e712

mentioned in issue #200 (closed)

added enhancement label