B2CC 2023 superliaison tasks
B2CC
Only Analysis Productions for TURBO dataset by now.
Modes:
-
🟢
-
🟢
-
🟢
-
(only LL for 2023) 🟢
-
🟢
-
🟢
-
🟢
-
(we are missing the line, to be followed later)
Merge request reports
Activity
removed SL label
removed B2CC label
added B2CC label
added SL label
- Resolved by Xiaofan Hu
I would encourage merging all the configured jobs together under one job and one analysis / production name (e.g.
b2cc_superliaison
) as each appear to process the same BK path, unless there is a good reason to keep them separate
removed SL label
added 2 commits
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
- Resolved by Peilian Li
Thanks a lot @xihu for preparing the MR. I should have made it clear that we may look at
Detached
lines. I made several suggestions, could you please check and apply if they look good to you.requested review from @oozcelik
- b2cc_turbo_superliaison/info.yaml 0 → 100644
28 bk_query: "/LHCb/Commissioning23/Beam6800GeV-VeloClosed-MagDown-Excl-UT/Real Data/SprucingPass23/94000000/B2CC.DST" 29 dq_flags: 30 - OK 31 - UNCHECKED 32 options: 33 entrypoint: b2cc_turbo_superliaison.dv_BdToJpsiKshortLL:main 34 extra_options: 35 input_type: ROOT 36 input_process: "TurboPass" 37 input_stream: b2cc 38 input_raw_format: 0.5 39 simulation: False 40 data_type: "Upgrade" 41 geometry_version: trunk 42 conditions_version: master 43 BdToJpsiKstar_TurboPass_MagDown: See a good example here.
At first glance, I strongly suggest to add
-
"ISMUON": F.ISMUON
variable which is quite powerful to clean up the backgrounds from my experiences. - HLT1 info for some widely used lines within B2CC
Hlt1_decisions = [ 'Hlt1TrackMVADecision', 'Hlt1TwoTrackMVADecision', 'Hlt1OneMuonTrackLineDecision', 'Hlt1DiMuonHighMassDecision', 'Hlt1TrackMuonMVADecision' ] evt_variables += SelectionInfo(selection_type="Hlt2", trigger_lines=[line_name])
- I would also suggest to add track chi2
"TRCHI2DOF": F.CHI2DOF,
- I am curious about this as it was not working as it should be earlier. Would be nice to compare with MCs. - Can we also add variables below as they are important for the quick detector commissioning checks :
evt_variables += FunctorCollection({ "RUNNUMBER": F.RUNNUMBER(odin), "EVENTNUMBER": F.EVENTNUMBER(odin), "nTracks": F.VALUE_OR(-1) @ F.RECSUMMARY_INFO(rec_summary, "nTracks"), "nPVs": F.VALUE_OR(-1) @ F.RECSUMMARY_INFO(rec_summary, "nPVs"), "nFTClusters": F.VALUE_OR(-1) @ F.RECSUMMARY_INFO(rec_summary, "nFTClusters")
Edited by Ozlem Ozcelik-
I added my 2 cents above @xihu please let me know if you need any help for implementing those.
changed this line in version 12 of the diff
unassigned @roneil
removed review request for @roneil
Hi Xiaofan, Would it be possible to include these two exclusive line channels, BuToChicKPlus and BuToJpsiKstPlus? I made one related MR before (!571 (merged)) and it would be great if you could add these two photon-involved channels.
- Resolved by Xiaofan Hu
Welcome to Analysis Productions!There are no existing analyses under the name
b2cc_turbo_superliaison
. This is the first!Pipeline #6167855
b2cc_turbo_superliaison
will process 0.0B of data and create about 2.0GB across 7 samples. The highest memory usage in tests was 3.3GB.Next steps
The request will be submitted to DIRAC.
Not sure what's happening? Check out our Getting Started documentation.
N.B. this is an automated message from the friendly Analysis Productions Bot.
Edited by LHCb Data Processing and Analysis
added 1 commit
- 4dd54aea - IsMuon, TrackCHI2DOF, Hlt1 decisions, and event variables;
assigned to @oozcelik