Skip to content

Bug fix for BandQ, B2CC/BnoC dimuon builder: lifetime resolution bias

Mengzhen Wang requested to merge mengzhen/bpvdls_fix_bandq_b2cc into 2024-patches

Test result about Jpsi efficiencies before and after the bug fix

Tested using the MR status in 2024/May/21, 17:14 CEST

Test Sample

Sample 1 : Inclusive Jpsi->MuMu, containing about 80% prompt Jpsi and 20% from-b Jpsi.

sim+std://MC/Dev/Beam6800GeV-expected-2024-MagDown-Nu7.6-25ns-Pythia8/Sim10c/24142001/DIGI

root://gridproxy@lhcbdcache-kit.gridka.de:1094//pnfs/gridka.de/lhcb/LHCb-Disk/lhcb/MC/Dev/DIGI/00212728/0000/00212728_00000099_1.digi

Sample 2: exclusive B->JpsiK sample

sim+std://MC/Dev/Beam6800GeV-expected-2024-MagDown-Nu7.6-25ns-Pythia8/Sim10c/12143001/DIGI

root://xrootd-lhcb.cr.cnaf.infn.it:1094//storage/gpfs_lhcb/disk/lhcb/MC/Dev/DIGI/00205044/0000/00205044_00000001_1.digi

Test result using 2024-patches (note: the full chain of hlt1->hlt2->sprucing is done. For 2024-patches and this-MR test, the same input is used for hlt1 option file. One can just look at the final yield for comparison, do not need to check the efficiency especially for sprucing, as the hlt2 is different for these two sectors.)

Inclusive Jpsi->MuMu:

LAZY_AND: SpruceBandQ_JpsiToMuMuDetached                #=219     Sum=114         
LAZY_AND: SpruceBandQ_JpsiToMuMuTightPrompt             #=219     Sum=118        
LAZY_AND: Hlt2_JpsiToMuMuDetachedFull                   #=767     Sum=130         
LAZY_AND: Hlt2_JpsiToMuMu                               #=767     Sum=335         
LAZY_AND: Hlt2_DiMuonJPsiTightFull                      #=767     Sum=144         

exclusive B->JpsiK

LAZY_AND: SpruceBandQ_JpsiToMuMuDetached                #=553     Sum=454        
LAZY_AND: SpruceBandQ_JpsiToMuMuTightPrompt             #=553     Sum=235        
LAZY_AND: Hlt2_JpsiToMuMuDetachedFull                   #=933     Sum=535         
LAZY_AND: Hlt2_JpsiToMuMu                               #=933     Sum=584         
LAZY_AND: Hlt2_DiMuonJPsiTightFull                      #=933     Sum=273         

Test result using this MR's update (note: the full chain of hlt1->hlt2->sprucing is done. For 2024-patches and this-MR test, the same input is used for hlt1 option file. One can just look at the final yield for comparison, do not need to check the efficiency especially for sprucing, as the hlt2 is different for these two sectors.)

Inclusive Jpsi->MuMu:

LAZY_AND: SpruceBandQ_JpsiToMuMuDetached          #=312     Sum=114         
LAZY_AND: SpruceBandQ_JpsiToMuMuTightPrompt       #=312     Sum=197         
LAZY_AND: Hlt2_JpsiToMuMuDetachedFull             #=767     Sum=130         
LAZY_AND: Hlt2_JpsiToMuMu                         #=767     Sum=541         
LAZY_AND: Hlt2_DiMuonJPsiTightFull                #=767     Sum=236         

exclusive B->JpsiK

LAZY_AND: SpruceBandQ_JpsiToMuMuDetached          #=562     Sum=454         
LAZY_AND: SpruceBandQ_JpsiToMuMuTightPrompt       #=562     Sum=243         
LAZY_AND: Hlt2_JpsiToMuMuDetachedFull             #=933     Sum=535         
LAZY_AND: Hlt2_JpsiToMuMu                         #=933     Sum=602         
LAZY_AND: Hlt2_DiMuonJPsiTightFull                #=933     Sum=282         

Historical message

This is a draft MR for discussion. Probably a bug fix.

When investigating the early 2024 MC, I noticed a lifetime asymmetry for BandQ upsilon sample. One can reproduce the result using the output of https://lhcb-analysis-productions.web.cern.ch/productions/?wg=bandq&analysis=quarkoniatomumu2024&ver=v0r0p7182118&dset=inclusive_upsilon1s_mc_24_nu7_6_magdown_veloclosed_root , and do DecayTree->Draw("QQbar_END_VZ - QQbar_BPVZ>>h100(100,-2,2)", "QQbar_TRUEID==553").

But if we do it in RD Upsilon output (Many thanks to @rquaglia for suggestion of including RD line in AP !) the lifetime bias disappear. One can check it in https://lhcb-analysis-productions.web.cern.ch/productions/?wg=bandq&analysis=quarkoniatomumu2024&ver=v0r0p7182118&dset=inclusive_upsilon1s_rd_mc_24_nu7_6_magdown_veloclosed_root , and do DecayTree->Draw("QQbar_END_VZ - QQbar_BPVZ>>h100(100,-2,2)", "QQbar_TRUEID==553").

One can find the result by doing DecayTree->Draw("QQbar_BPVDLS>>h100(100,-5,5)","QQbar_TRUEID==553") for both sample. The BPVDLS negative part is missing. This is due to the cut here .

I confirm BandQ lines are generally influenced, including the early measurement lines. The tz-fit for prompt/from-b separation will be more challenging. c.c. to @lcapriot @zexu .

I suspect that B2CC lines are also influenced. The make_jpsi() at https://gitlab.cern.ch/lhcb/Moore/-/blob/master/Hlt/Hlt2Conf/python/Hlt2Conf/lines/b_to_charmonia/b_to_jpsix.py?ref_type=heads#L17 is taken from our shared directory. It would be appreciated if @oozcelik @yimingli can kindly have a look.

If both WGs are influenced, need a greenlight from conveners from both WGs before we move to the standard RTA/DPA review. From B&Q side, I will do a local test of hlt1->hlt2->sprucing->tuple to see if this MR really fixes the lifetime resolution bias issue. If not we just close it.

If B2CC is also influenced, it would be super appreciated an independent local cross-check can be made. We have a few quarkonia->mumu and b2psiX MC samples available at: /MC/expected-2024.Q1.2/Beam6800GeV-expected-2024.Q1.2-MagDown-Nu7.6-25ns-Pythia8/Sim10c

Not sure which labels to add. I will think about it after finishing the local test tomorrow. Necessary ones to the best of my knowledge are added.

Edited by Mengzhen Wang

Merge request reports

Loading