[QEE] EW Tupling y24v0 : First 2024 Data+MC
First Tupling over the Spruced Comm24 data + exp24 MC.
MC needs processing through Hlt1->Hlt2->Spruce ourselves before we can tuple.
Related to: https://gitlab.cern.ch/LHCb-QEE/ew-analyses/-/milestones/6#tab-issues
(Part of the Run3 ew-analyses framework
development: see Wiki ).
Built relative to !1041 (merged).
Changes:
for ease of reading
288b45dc
2024MC information :Loop over polarity for MC now.
Grid requires v2 optimisation binaryTag. See: https://mattermost.web.cern.ch/lhcb/pl/uumk1hze83gn7ddirj7xequq1r
Update MC bkk path with the following information:
- lhcb-simulation/mc-requests!479 (merged)
- /MC/expected-2024.Q1.2/Beam6800GeV-expected-2024.Q1.2-MagDown-Nu7.6-25ns-Pythia8/Sim10c/{event-type}/DIGI
- DDDB: dddb-20240311 Condition DB: sim-20231017-vc-mu100
84990d33
ZTau MC + Rec_Summary Variables :Added a Ztau MCDecayTree now we have it available from lhcb-simulation/mc-requests!479 (merged).
Also added several rec_summary variables from https://codimd.web.cern.ch/DDyKwH0JRQWAFuUFG8I7sw#. Specifically:
["nPVs", "nLongTracks", "nFTClusters", "nVPClusters", "nEcalClusters", "hCalTot"]
4037c414
2024 DATA BKK + New Moore Versions :2024 data bkk for Full and TurCal.
2024 Moore versions : corresponding to https://gitlab.cern.ch/lhcb-core/lhcbstacks/-/blob/master/data/stacks/DPA/2024.04.22.yml
{%- set hlt1_v = 'v55r7' %} # Moore latest `2024-patches` release as of 22-Apr-24
{%- set hlt2_v = 'v55r7' %}
{%- set spruce_v = 'v55r7' %}
Added keep_running to the Data job -> Not entirely confident how this works
f451181f.
Remove unnecessary CC from decay descriptors :Should have no effect on anything except the log will stop correctly complaining about unnecessary conjugation of self conjugating decays.
ae844aae.
New HLT/Spruce MC scripts for the new version :https://mattermost.web.cern.ch/lhcb/pl/c6jkuzibcjnb3mc9j55r4teduc.
HLT1 : Stolen verbatim from Hlt/Hlt1Conf/options/hlt1_pp_expected_24_without_UT.py on v55r7.
HLT2 : Stolen and adapted from Hlt/Hlt2Conf/options/hlt2_pp_expected_24_without_UT.py on v55r7.
- Only adaptation was changing which lines ran :)
Spruce : The different streaming configurations stolen from the following on v55r7:
- Turbo: Hlt/Hlt2Conf/options/sprucing/sprucepass_pp_expected_24.py.
- Full: Hlt/Hlt2Conf/options/sprucing/spruce_pp_expected_24.py.
And Removed reco binds as per !1119 (comment 7859546).
ea7d628d + 8d1159cf
TurCal changes to info.yaml and spruce.py :TurCal Sprucing option stolen:
TurCal: Hlt/Hlt2Conf/python/Hlt2Conf/sprucing_settings/Sprucing_production_PP_24c1.py
43e3cee0
2024-like Tupling :QEE's Hlt2 full-stream linenames now have Full
at the end.
We also now can't tistos TrkEff as they exist in their own stream.
ZTrkEff is now 4 selections, before we merged them at Sprucing but with the automatic TurCal spruceline definitions we just duplicate the Hlt2 lines.
There were several places we used spec.isFull
to distinguish between Full and Turbo.
Now replaced by spec.varName
to distinguish the three streams.
See: !1059 (comment 7904296) + !1059 (comment 7904297) + !1059 (comment 7905971) for the explicit code changes.
Iterating over MagPol + adding TurCal + changing inputs all change the Enums:
function names are now:
{Full/Turbo/TurCal}_{Comm24/exp24}_{MagDown, MagUp}
.
See: !1059 (comment 7904298) for how extra_event_info changed.
caf56dbb + 6d9e1668
Adding appropriate geometry version :!1059 (comment 7907247) for details.
Selection to Line Map
map
selection_linename_map
# Stream : { selection : linename }
Stream.Turbo: {
"Jpsi_Detached": "Hlt2QEE_JpsiToMuMu_Detached",
"Jpsi_Prompt": "Hlt2QEE_JpsiToMuMu_Prompt",
"U1S": "Hlt2QEE_Upsilon1SToMuMu",
},
Stream.Full: {
"Z": "SpruceQEE_ZToMuMu",
"ZMuID": "SpruceQEE_ZToMuMu_SingleNoMuID",
"Wp": "SpruceQEE_SingleHighPtMuon",
"Wm": "SpruceQEE_SingleHighPtMuon",
"WpNoMuID": "SpruceQEE_SingleHighPtMuonNoMuID",
"WmNoMuID": "SpruceQEE_SingleHighPtMuonNoMuID",
"ZSS": "SpruceQEE_DiMuonSameSign",
},
Stream.TurCal:{
"ZTrkEff_VeloMuon_mum": "SpruceTurCalTrackEff_ZToMuMu_VeloMuon_mum_Tag",
"ZTrkEff_VeloMuon_mup": "SpruceTurCalTrackEff_ZToMuMu_VeloMuon_mup_Tag",
"ZTrkEff_SeedMuon_mum": "SpruceTurCalTrackEff_ZToMuMu_SeedMuon_mum_Tag",
"ZTrkEff_SeedMuon_mup": "SpruceTurCalTrackEff_ZToMuMu_SeedMuon_mup_Tag"
},
ToDo:
-
Add all the extra variables for EM evaluations (nHits, nTracks, etc.) - Added several from rec_summary. Do we need any more? Not as far as I know
- see: !1059 (comment 7917627)
-
POSTPONED
- Hlt1 MC processing still needs improvements:
- Flagging Modes + Prescale/postscale removal like 2023-hlt1pp-patches
- lhcb/Moore!3219 (closed) thus new release -> Postponed
-
POSTPONED See: !1059 (comment 7910109) - mc_particles location. Fix from https://gitlab.cern.ch/LHCb-QEE/ew/ew-analyses/-/issues/911 doesn't seem to work (breaks the MCDecayTrees?)
-
How does keep_running
work on DATA APs?