ReWGProd Run2_D02KsHH
Issues in clone track in Prompt sample and DTF problems in double-tagged sample. I think we should resubmit the whole sample because of TupleToolTrackInfo
.
-
DONE - Add WS double-tagged sample to the same Ntuple. - avoid asking for WGProd twice -
DONE - Add TupleToolTrackInfo to study/exclude clone tracks which share same VELO hit - comments from Prompt WG review -
Leave as it is - Change ‘Beauty’ to ‘B0’ and ‘X’ to ‘D0’ ? -
Fix the issue in the different behavior between Dst_DTF_D0_CTAU (LoKi::Hybrid::DTFDict)
andB_ReFit_D0_ctau (TupleToolDecayTreeFitter)
in the double-tagged sample.
Open question:
- For SL sample, should we wait for Restripping 2016 and 2017 sample?
[DONE] 2. Should we ask for WGProd for the LTUNB line?
Following the KsHH meeting on Tuesday and other discussions, I think it would be nice to discuss here. @njurik @kafische @mhilton @sstahl @mamartin @tnanut
Edited by Surapat Ek-In