Fix D02hhpi0 lines

The lines were extremely subperformant due to a cut to the DOCACHI2 variable in the D*+->D0pi builder (this is also evincible from !2414 (closed)). The D*+->D0pi builder has been substituted with the same used for the D0->hh decays defined in taggers.py.

Rates before and after:

Hlt2 line	rate before [kHz]	rate after [kHz]
Hlt2Charm_DstpToD0Pip_D0ToKmKpPi0_MDecision	0.0 +/- 0.0	0.0 +/- 0.0
Hlt2Charm_DstpToD0Pip_D0ToKmKpPi0_RDecision	0.0 +/- 0.0	0.20022 +/- 0.1155
Hlt2Charm_DstpToD0Pip_D0ToKmPipPi0_MDecision	0.0 +/- 0.0	0.0 +/- 0.0
Hlt2Charm_DstpToD0Pip_D0ToKmPipPi0_RDecision	0.06674 +/- 0.0667	1.20136 +/- 0.2829
Hlt2Charm_DstpToD0Pip_D0ToPimPipPi0_MDecision	0.0 +/- 0.0	0.33371 +/- 0.1492
Hlt2Charm_DstpToD0Pip_D0ToPimPipPi0_RDecision	0.06674 +/- 0.0667	1.60181 +/- 0.3267

added Charm label

assigned to @fsouzade, @lpica, and @roneil

added bug fix hlt2 selection labels

If you can address the CI failure here https://gitlab.cern.ch/lhcb/Moore/-/jobs/30314407 we can get a test started

mentioned in merge request !2420 (merged)

added 1 commit

• 0601438b - fix D02hhpi0 Hlt2 lines

Compare with previous version

added RTA label

added 1 commit

• 25980c18 - ignoring unrelated file

Compare with previous version

marked this merge request as draft

marked this merge request as ready

Aren't new rates too high? Is there some additional tuning expected?

Also seems that current changes are not what is intended for this MR.

@msaur thanks for reviewing this. The rates are high but not incredibly high, in fact they are still smaller than D0->hh rates. Moreover, yes they are expected to be tuned as soon we will get the MC or understand why we did't see signal events in 2022 so far. The MR cited refers to the fact that the DOCACHI2 cut on the D+ should be avoided and this is satisfied in this MR where we use the same builder for D+->D0pi decays as we used for D0->hh.

We can get a test started if you address the linter messages in the failing CI job.

added 1 commit

• 2f10a751 - fix linter message

Compare with previous version

mentioned in issue #598 (closed)

mentioned in issue #599 (closed)

mentioned in issue #623 (closed)

Hi @smaccoli, please could you apply the fix for check-formatting, I can then run the ci-tests

added 1 commit

• 9b34c01e - Fixed formatting

Compare with previous version

resolved all threads

/ci-test

added ci-test-triggered label

• [2023-07-28 11:15] Validation started with lhcb-master-mr#8684
• [2023-08-14 12:20] Validation started with lhcb-master-mr#8914

mentioned in issue #627 (closed)

mentioned in issue #634 (closed)

Looks like this MR got stuck in testing? Perhaps we need to launch another test?

added June-2023-data label

changed milestone to %RTA/2023.08.24

added PR/Moore_hlt2_bandwidth label

/ci-test

resolved all threads

approved this merge request

merged

mentioned in commit 597fb866