2019-07-15 Stripping v14r2p1

Release for S21rxp2 restrippings after overtiming fixes

Based on Phys v21r1p2 This version is released on stripping21-patches branch.

• S21 dbase and archives, !1247 (@nskidmor)

• fix to B&Q and QEE dictionaries, !1241 (@nskidmor)

• Update RD dictionatires for overtime fixes, !1239 (@vlisovsk)

• Overtiming fix for Beauty2XGamma4pi line, !1238 (@cremonal)
  @vlisovsk @iwilliam @vibellee

  Protecting B2XG4pi against busy events by adding GECs (in this line only): nTracks < 500 & nSPD < 600

  FILE TO MERGE: StrippingBeauty2XGamma.py

  After applying these GECs, the largest timing is found to be within the limit (<10s):

  TimingAuditor.TIMER INFO StrippingBeauty2XGamma4pi_Line | 1.851 | 1.856 | 0.048 769.0 7.28 | 52977 | 98.348 |

• Overtiming fix for Kshort2Leptons lines, !1237 (@vlisovsk)
  Tested.

• Add 18 new lines in B2OC Stripping Settings for S21rXp2, !1234 (@shunan)

• Add 18 new DDLambda lines to stripping21-patches, !1232 (@abertoli)

• add timing fixes and update line config dicts for s21rXp2 for QEE, !1229 (@mmarinan)

• BandQ s21rXp2 timing fixed, !1226 (@vazhovko)
  Test using RDST2 file:

  TimingAuditor.TIMER              INFO          StrippingXibcBDT_XibcP2DpKLine                     |     0.652 |     0.654 |    0.019      22.5     0.64 |   53082 |    34.719 |  
  TimingAuditor.TIMER              INFO           StrippingXibcBDT_XibcP2DpKLinePreScaler           |     0.002 |     0.003 |    0.002       0.1     0.00 |   53082 |     0.183 |  
  TimingAuditor.TIMER              INFO           StrippingXibcBDT_XibcP2DpKLineFilterSequence      |     0.614 |     0.616 |    0.002      22.5     0.64 |   53082 |    32.706 |  
  TimingAuditor.TIMER              INFO            XibcBDTSelUnPions_comb                           |     0.127 |     0.129 |    0.005      12.4     0.11 |   52517 |     6.784 |  
  TimingAuditor.TIMER              INFO            XibcBDTSelUnKaons_comb                           |     0.069 |     0.071 |    0.004       4.5     0.06 |   52047 |     3.703 |  
  TimingAuditor.TIMER              INFO            XibcBDTSelDplus_comb                             |     0.222 |     0.224 |    0.042       9.4     0.28 |   50482 |    11.354 |  
  TimingAuditor.TIMER              INFO            XibcBDTSelDplus                                  |     0.015 |     0.017 |    0.006       0.4     0.01 |    9237 |     0.159 |  
  TimingAuditor.TIMER              INFO            XibcBDTSelXibcP2DpK                              |     0.499 |     0.502 |    0.052      17.0     0.67 |    4399 |     2.208 |  
  TimingAuditor.TIMER              INFO            XibcBDT_XibcP2DpKLine                            |     0.682 |     0.686 |    0.241      12.2     0.61 |    1362 |     0.935 |  
  TimingAuditor.TIMER              INFO           StrippingXibcBDT_XibcP2DpKLinePostScaler          |     0.002 |     0.003 |    0.003       0.0     0.00 |     190 |     0.001 |  
  

• tighten stripping B2SS, !1225 (@jcidvida)
  I run tests in the conflicting dsts, below is what I get. These are the lines for which I get at least one event with t>10s in any of the dsts. The different values correspond to the times in s corresponding to different dsts, when above 10s.

  StrippingB2SSB2KstSSKaonDetLine 2 ['13.99', '13.53']

  StrippingB2SSB2KstSSPionDetLine 1 ['12.68']

  StrippingB2SSB2KstSSProtonDetLine 2 ['63.05', '24.34']

  StrippingB2SSB2KstSSProtonLine 1 ['12.23']

  StrippingB2SSBu2KSSProtonDetLine 2 ['24.22', '13.51']

  I would say the StrippingB2SSB2KstSSProtonDetLine and StrippingB2SSBu2KSSProtonDetLine are still problematic. This is a big improvement with respect to how things were, but still not the exact goal. So up to the conveners to decide. If this is not acceptable, please leave these two lines out

• documentaion fix, !1223 (@nskidmor)

• B2OC selections for 2011/2012 overtime, !1219 (@abertoli)
  only one line affected:
  Lb2sigmacpp4PiSigmacpp2LcPiLc2PKPi
  actions for it:
  _ < 500 candidates cut
  _ ADAMASS('Sigma_c++') < 100 MeV (affect both Sigma_c++ lines B2OC has)

• TrackEff DownMuon overtime 'fix', !1216 (@rekopecn)
  This line takes longer due to the need of reconstructing DownMuon tracks in the stripping line. Small change in seed P and PT was made (1500=>0 MeV and 0=>200 MeV)

  Tested on the first DST sample, maximal times decreased from 12 and 18 seconds to 0.6 and 14 seconds, log below.

  TimingAuditor.TIMER              INFO          StrippingTrackEffDownMuonLine1                     |    12.203 |    12.327 |    0.045    1252.4    44.85 |   10000 |   123.271 |  
  TimingAuditor.TIMER              INFO          StrippingTrackEffDownMuonLine2                     |    13.052 |    13.461 |    0.032   18111.3   186.74 |   10000 |   134.618 |  
  
  TimingAuditor.TIMER              INFO          StrippingTrackEffDownMuonLine1                     |    11.861 |    11.976 |    0.045     644.7    42.43 |   10000 |   119.763 |  
  TimingAuditor.TIMER              INFO          StrippingTrackEffDownMuonLine2                     |    12.669 |    12.803 |    0.035   14587.7   152.51 |   10000 |   128.032 |  
  

• Update of Calib Run 1 settings (solving overtimings in CaloPID and new line), !1215 (@lohenry)

• CaloPID line improvements (Run1), !1211 (@chefdevi)
  Modification of 2 calo lines. Before/after rate comparison done without re-running the calo reco on 2012 data (i.e. commenting out #importOptions("$STRIPPINGSELECTIONSROOT/tests/users/DV-RedoCaloPID-Stripping21.py") in user test script to allow running over more stat in a shorter time. Test with re-running the calo-reco will follow, hence the WIP).

---

Ds* -> Ds gamma from StrippingCaloPID.py had too high timing due to use of StdLooseDplus2KKPi. Now use StdVeryTightDsplus2KKPi which implement P & PID cut on daughters. These cuts were present at a later stage anyway in my selections, so no signal is lost.

Rate test over 50k with StdLooseDplus2KKPi:

StrippingReport INFO Event 50000, Good event 50000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |!StrippingCaloPIDDsst2DsGammaLine | 0.0280| 14| 1.143| 15.584| |!StrippingCaloPIDDsst2DsGammaLine_TIMING | 0.0280| 14| 1.143| 0.036|

Rate test over 50k with StdVeryTightDsplus2KKPi:

StrippingReport INFO Event 50000, Good event 50000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |!StrippingCaloPIDDsst2DsGammaLine | 0.0280| 14| 1.143| 2.769| |!StrippingCaloPIDDsst2DsGammaLine_TIMING | 0.0280| 14| 1.143| 0.035|

-> factor of 5 improvement on timing for same physics output.

---

D0 -> K pi gamma from StrippingD02KPiGamma.py. This line was heavily pre-scaled (5%) due to the large retention rate (despite a large 2 GeV PT cut on the photon). To reduce the rate and remove the prescale, the D* -> D0 pi+ decay was reconstructed by adding a slow pion. A new stripping line is created: StrippingDst2D0Pi.py, the previous D02KPiGamma line can be ignored in the upcoming stripping campaigns.

Rate test over 50k without reco of the slow pion and 5% prescale:

StrippingReport INFO Event 50000, Good event 50000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0300| 15| | 9.801| |_StrippingSequenceStreamCalibration_ | 0.0300| 15| | 9.787| |!StrippingD02KPiGamma | 0.0140| 7| 1.143| 1.679| |!StrippingD02KPiGamma_TIMING | 0.0160| 8| 1.250| 1.687|

Rate test over 50k with reco of the slow pion and no prescale:

StrippingReport INFO Event 50000, Good event 50000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0040| 2| | 15.793| |_StrippingSequenceStreamCalibration_ | 0.0040| 2| | 15.777| |!StrippingDst2D0Pi | 0.0040| 2| 1.000| 9.276| |!StrippingDst2D0P_TIMING | 0.0040| 2| 1.000| 0.040|

-> factor of 10 improvement on retention rate at the cost of increased timing (not sure why). If necessary a prescale of 0.5 could be introduced.

---

Rate tests with re-running the calo on 2011 & 2012 data will follow.

---

Rate tests re-running the calo reconstruction.

Reminder: those lines are for calo PID: they go to full DST and save the calo raw banks. They can exceed the limit of 0.01% retention rate. For more precise rate, see the results previously posted (over 50k + calo repro should not change the rates significantly).

CaloPID 2011

StrippingReport INFO Event 10000, Good event 10000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0100| 1| | 3.147| |_StrippingSequenceStreamCalibration_ | 0.0100| 1| | 3.130| |!StrippingCaloPIDDsst2DsGammaLine | 0.0100| 1| 1.000| 0.891| |!StrippingCaloPIDDsst2DsGammaLine_TIMING | 0.0100| 1| 1.000| 0.035|

CaloPID 2012

StrippingReport INFO Event 10000, Good event 10000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0500| 5| | 6.402| |_StrippingSequenceStreamCalibration_ | 0.0500| 5| | 6.384| |!StrippingCaloPIDDs2EtapPiLine | 0.0400| 4| 1.000| 2.198| |!StrippingCaloPIDDsst2DsGammaLine | 0.0100| 1| 1.000| 2.949| |!StrippingCaloPIDDs2EtapPiLine_TIMING | 0.0400| 4| 1.000| 0.047| |!StrippingCaloPIDDsst2DsGammaLine_TIMING | 0.0100| 1| 1.000| 0.038|

Dst2D0Pi 2011

StrippingReport INFO Event 10000, Good event 10000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0100| 1| | 2.406| |_StrippingSequenceStreamCalibration_ | 0.0100| 1| | 2.387| |!StrippingDst2D0Pi | 0.0100| 1| 1.000| 1.736| |!StrippingDst2D0P_TIMING | 0.0100| 1| 1.000| 0.041|

Dst2D0Pi 2012

StrippingReport INFO Event 10000, Good event 10000 | *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*| |_StrippingGlobal_ | 0.0100| 1| | 3.530| |_StrippingSequenceStreamCalibration_ | 0.0100| 1| | 3.510| |!StrippingDst2D0Pi | 0.0100| 1| 1.000| 2.755| |!StrippingDst2D0P_TIMING | 0.0100| 1| 1.000| 0.043|