Skip to content

Add StrippingB2DMuNuX_D_Electron lines to Run1 re-stripping

Florian Reiss requested to merge freiss_Run1_stripping into stripping21-patches

propagating the StrippingB2DMuNuX_D_Electron lines to the Run1 re-stripping.

The added lines are:

  • StrippingB2DMuNuX_D0_Electron
  • StrippingB2DMuNuX_Dp_Electron
  • StrippingB2DMuNuX_Ds_Electron
  • StrippingB2DMuNuX_Lc_Electron

The modified files are:

  • Phys/StrippingSelections/python/StrippingSelections/StrippingSL/StrippingB2DMuNuX.py
  • Phys/StrippingSettings/python/StrippingSettings/Stripping21r0p2/LineConfigDictionaries_Semileptonic.py
  • Phys/StrippingSettings/python/StrippingSettings/Stripping21r1p2/LineConfigDictionaries_Semileptonic.py

Rates 2011:

StrippingReport                                                INFO Event 100000, Good event 100000
 |                                              *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
 |_StrippingGlobal_                                            |  0.2220|       222|       |   4.160|
 |_StrippingSequenceStreamSemileptonic_                        |  0.2040|       204|       |   3.827|
 |!StrippingB2DMuNuX_D0_Electron                               |  0.0340|        34|  1.059|   1.256|
 |!StrippingB2DMuNuX_Dp_Electron                               |  0.0170|        17|  1.000|   0.064|
 |!StrippingB2DMuNuX_Ds_Electron                               |  0.0250|        25|  1.280|   0.062|
 |!StrippingB2DMuNuX_Lc_Electron                               |  0.0040|         4|  1.000|   0.085|
 |!StrippingB2DMuNuX_D0_Electro_TIMING                         |  0.0340|        34|  1.059|   0.047|
 |!StrippingB2DMuNuX_Dp_Electro_TIMING                         |  0.0170|        17|  1.000|   0.043|
 |!StrippingB2DMuNuX_Ds_Electro_TIMING                         |  0.0250|        25|  1.280|   0.044|
 |!StrippingB2DMuNuX_Lc_Electro_TIMING                         |  0.0040|         4|  1.000|   0.042|

Rates 2012:

StrippingReport                                                INFO Event 100000, Good event 100000
 |                                              *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
 |_StrippingGlobal_                                            |  0.8400|       840|       |   6.558|
 |_StrippingSequenceStreamSemileptonic_                        |  0.7980|       798|       |   6.161|
 |!StrippingB2DMuNuX_D0_Electron                               |  0.0970|        97|  1.041|   2.089|
 |!StrippingB2DMuNuX_Dp_Electron                               |  0.1080|       108|  1.037|   0.146|
 |!StrippingB2DMuNuX_Ds_Electron                               |  0.0880|        88|  1.261|   0.136|
 |!StrippingB2DMuNuX_Lc_Electron                               |  0.0200|        20|  1.100|   0.228|
 |!StrippingB2DMuNuX_D0_Electro_TIMING                         |  0.0970|        97|  1.041|   0.057|
 |!StrippingB2DMuNuX_Dp_Electro_TIMING                         |  0.1080|       108|  1.037|   0.051|
 |!StrippingB2DMuNuX_Ds_Electro_TIMING                         |  0.0880|        88|  1.261|   0.053|
 |!StrippingB2DMuNuX_Lc_Electro_TIMING                         |  0.0200|        20|  1.100|   0.049|

@cvazquez @nskidmor I realize that the rates for some of the added lines are above the limit, but I would argue that it is still reasonable since each contains two final states, but please let me know what you think.

Edited by Carlos Vazquez Sierra

Merge request reports