Skip to content

Fixed error found in data - rerun data tuples

Jake Lewis Amey requested to merge jamey/B02D0D0barKpi_rerun into master

This production is for an amplitude analysis of the B0→D0D0ˉK+π−B^0 \rightarrow D^0 \bar{D^0} K^+ \pi^-B0→D0D0ˉK+π− decay, with either (D0→K−π+)(D0ˉ→K+π−)(D^0 \rightarrow K^- \pi^+) (\bar{D^0} \rightarrow K^+ \pi^-)(D0→K−π+)(D0ˉ→K+π−), (D0→K−π+π+π−)(D0ˉ→K+π−)(D^0 \rightarrow K^- \pi^+ \pi^+ \pi^-) (\bar{D^0} \rightarrow K^+ \pi^-)(D0→K−π+π+π−)(D0ˉ→K+π−) or (D0→K−π+)(D0ˉ→K+π−π−π+)(D^0 \rightarrow K^- \pi^+) (\bar{D^0} \rightarrow K^+ \pi^- \pi^- \pi^+)(D0→K−π+)(D0ˉ→K+π−π−π+).

The analysis follows from the branching fraction measurement of this decay, and adds 2017 and 2018 data as well as D→K3πD \rightarrow K 3\piD→K3π sub-decays.

This will not supersede any previous productions.

Example tuples can be found in /eos/lhcb/user/j/jamey/AProd_examples/

This merge will just re-run the data tuples due to an error affecting very few essential branches that has been recently discovered. The bug causing this has now been fixed.

Instructions

When creating your merge request:

  • Add a label for your WG
  • Mark as "WIP:" until you're happy with the CI results
  • If the merge request supersedes a previous one, add a comment at the end of the header: (supersedes !<MR number>). Please state explicitly in the description if the superseded ntuples can be deleted immediately, or after the new merge request is finalised

When ready:

  • Remove the "WIP:" from the title:
  • Assign the merge request to you working group's DPA/RTA liaison

To find your working group's DPA/RTA liaison, see this page:

https://twiki.cern.ch/twiki/bin/viewauth/LHCbPhysics/LHCbWGLiaisons

Edited by Aidan Richard Wiederhold

Merge request reports