Bs0 -> D(s) D(s) phi data for Run1/2

$B_s^0 \rightarrow D^{\pm}D^{\mp} \phi$

,

$B_s^0 \rightarrow D_s^{\pm}D_s^{\mp} \phi$

,

$B_s^0 \rightarrow D^{*\pm}D^{\mp} \phi$

and

$B_s^0 \rightarrow D^{*\pm}D^{*\mp} \phi$

data for run 1 and run2, where

$\phi \rightarrow K^{\pm} K^{\mp}$

.

using the following line

B2DDphi_B2DDPhiLine
B2DDphi_B2DsDsPhiLine
B2DDphi_B2DstDpPhiLine
B2DDphi_B2DstDstPhiLine

Instructions

Check our documentation for details of the submission process: https://lhcb-ap.docs.cern.ch/user_guide/submitting.html

If the samples created by your request will supersede older ones, please read the docs here for what you need to do: https://lhcb-ap.docs.cern.ch/user_guide/housekeeping.html#archiving-superseded-or-obsolete-outputs

If the merge request supersedes a previous one, add a comment at the end of the header: (supersedes !<MR number>).

added B2OC label

assigned to @jiangyi

Welcome to Analysis Productions!

This is a summary of the productions requested in this merge request:

Step	Production ID	Num Test LFNs	Run time	Estimated Output Size (MB)
2011_MagDown_collision_Bs2DDPhi	204738	1	0:05:09.822215	3.6
2011_MagUp_collision_Bs2DDPhi	204739	1	0:01:33.807586	0.9
2012_MagDown_collision_Bs2DDPhi	204740	1	0:26:12.298459	5.4
2012_MagUp_collision_Bs2DDPhi	204741	1	0:06:22.702756	6.7
2015_MagDown_collision_Bs2DDPhi	204742	1	0:08:46.452705	7.7
2015_MagUp_collision_Bs2DDPhi	204743	1	0:04:08.063641	6.6
2016_MagDown_collision_Bs2DDPhi	204744	1	0:06:34.485901	7.2
2016_MagUp_collision_Bs2DDPhi	204745	1	0:07:06.683104	7.2
2017_MagDown_collision_Bs2DDPhi	204746	1	0:07:29.798386	8.7
2017_MagUp_collision_Bs2DDPhi	204747	1	0:07:21.620341	9.2
2018_MagDown_collision_Bs2DDPhi	204748	1	0:07:15.088423	5.9
2018_MagUp_collision_Bs2DDPhi	204749	1	0:07:10.540276	13.5

added datarun1/2 label

marked this merge request as ready

requested review from @agilman and @canorman

Hi ! Do you understand the errors in the DaVinci output of the CI tests ? They seem to be pretty harmless and only due to a (very) few problematic events.

Concerning the size of the output, I would prefer to wait for @agilman's opinion because it is in the 1+ TB territory and I just want to be sure it's okay for this type of AP (I believe it is but I'm new to this).

The errors are almost due to the failed DTF. Some events are not able to get coverage with special constraint.

For the output size, I do not know how to reduce the size of it. I have tried to rebuild the decay chain, but the I can not make sure that if the K is from B or from Ds, then it would have too many combinations of K. If you have some idea, I can add it.

added 1 commit

• a116dd15 - add more cuts to reduce output size

Compare with previous version

resolved all threads

approved this merge request

merged

mentioned in commit 23db4c62

mentioned in issue #1327 (closed)

mentioned in commit 7f4d56d6