Add StrippingBc2Ds2MuMuLine
Added line for Bc+ -> Ds2* (-> D0 (-> K- pi+) K+) mu+ mu- decay, in addition SSLine is added too.
Rates and timing results for 2018:
StrippingReport INFO Event 10000, Good event 10000
| *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
|_StrippingGlobal_ | 0.0100| 1| | 4.865|
|_StrippingSequenceStreamDimuon_ | 0.0100| 1| | 4.856|
|!StrippingBc2Ds2MuMuLine | 0.0100| 1| 1.000| 3.920|
|!StrippingBc2Ds2MuMu_SSLine | 0.0000| 0| 0.000| 0.128|
|!StrippingBc2Ds2MuMuLine_TIMING | 0.0100| 1| 1.000| 0.023|
|!StrippingBc2Ds2MuMu_SSLine_TIMING | 0.0000| 0| 0.000| 0.027|
TBD:
-
tune the rate -
check the efficiency on MC
Updated rates and timing results (for 2018) on 17/Jul/2023:
StrippingReport INFO Event 100000, Good event 100000
| *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
|_StrippingGlobal_ | 0.0140| 14| | 5.176|
|_StrippingSequenceStreamDimuon_ | 0.0140| 14| | 5.163|
|!StrippingBc2Ds2MuMuLine | 0.0100| 10| 1.200| 4.085|
|!StrippingBc2Ds2MuMu_SSLine | 0.0050| 5| 1.200| 0.155|
|!StrippingBc2Ds2MuMuLine_TIMING | 0.0100| 10| 1.200| 0.042|
|!StrippingBc2Ds2MuMu_SSLine_TIMING | 0.0050| 5| 1.200| 0.030|
Merge request reports
Activity
assigned to @nsahoo
Hi @nsahoo. The rate of
StrippingBc2Ds2MuMu_SSLine
is 0.000. Can you try more events to estimate its rates? If production of MC used to estimate efficiency is completed?changed milestone to %2023 Re-Strip Campaign -- Development and Testing
removed all-slots label
- Resolved by Nate Grieser
@nsahoo It's likely this is just a really low rate line, but could you try running a 50k/100k event test just to ensure? (right now we only see 1 event)
- Resolved by Nate Grieser
- Resolved by Eduardo Rodrigues
added all-slots label
Hi @fredi this is what @ngrieser also asked for, and the rate with 100k was reported above. For completeness, here it's:
| *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0130| 13| | 5.119| |_StrippingSequenceStreamDimuon_ | 0.0130| 13| | 5.104| |!StrippingBc2Ds2MuMuLine | 0.0100| 10| 1.300| 4.016| |!StrippingBc2Ds2MuMu_SSLine | 0.0030| 3| 1.000| 0.148| |!StrippingBc2Ds2MuMuLine_TIMING | 0.0100| 10| 1.300| 0.038| |!StrippingBc2Ds2MuMu_SSLine_TIMING | 0.0030| 3| 1.000| 0.034|
I'm gonna do some tuning today and the MR should be in principle ready by tomorrow to get merged.
Edited by Niladri Sahoo@nsahoo have you finished with your developments here? If so, could you update the rates in the header to the most recent ones, and mark as ready so that it can be review?
@ngrieser apologies for the delay. I am now running the scripts to get the updated rates, the MR is gonna be ready in next few mins.
Edited by Niladri Sahooadded 1 commit
- 524f5140 - final run after tuning the cuts and using dilepton filter instead of...