Draft: DrellYan Low Mass Prompt Comm23
Related to LHCb-QEE/qee-hlt-run3#32
DrellYan process with Comm23 data, with the following HLT2
lines:
['Hlt2QEE_DiMuon_DrellYan_LowMass_OS_Prompt', 'Hlt2QEE_DiMuon_DrellYan_LowMass_SS_Prompt']
Instructions
When creating your merge request:
- Add a label for your WG
- Mark as "Draft:" until you're happy with the CI results
- If the merge request supersedes a previous one, add a comment at the end of the header:
(supersedes !<MR number>)
. Please state explicitly in the description if the superseded ntuples can be deleted immediately, or after the new merge request is finalised
When ready:
- Remove the "Draft:" from the title:
- Assign the merge request to you working group's DPA/RTA liaison
To find your working group's DPA/RTA liaison, see this page:
https://twiki.cern.ch/twiki/bin/viewauth/LHCbPhysics/LHCbWGLiaisons
Merge request reports
Activity
added QEE label
assigned to @odurmus
👋 Welcome to Analysis Productions!There are no existing analyses under the name
drellyan_sliaison
. This is the first!Pipeline #6226218
DrellYan_sliaison
will process 113.0TB of data and create about 1.1GB across 1 samples. The highest memory usage in tests was 3.7GB.Next steps
When happy with the result of tests and ready to proceed, remove
Draft:
from the merge request title.
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
Hi @odurmus, please assign me as reviewer when you think this is ready.
requested review from @rjhunter
Good morning @odurmus, before I get into the review, I'd like to understand: it seems that the only real difference between this and !688 (merged) is the bkk path of Collision23 or Commissioning23. I think that you can loop over different datasets in your
info.yaml
, such that you only need 1 production and 1 merge request. Could you try that please?It looks like !689 (merged) for example is doing exactly this loop.
The sprucing campaign tracker suggests this should have gone through sprucing pass-through.
I tried using spruced data rather than RAW but there were no proper output as far as I can tell (see). Here in the table it says Full stream for DY, with an asterisk, which suggests we will be able to use spruced data for Coll23.
In any case, I prepared the loop you suggested. I can push if you think that should be the case
Right, OK. I did some digging. The Drell-Yan lines were moved to Turbo for Moore v54r16 in Moore!2564. That was the last release before HLT2 ran over the Collision23 data. This means that the lines were in Full for Commissioning23, and so we'd need to run over the output of a sprucing line. The sprucing of Commissioning23 is ongoing, however, in any case we don't have any sprucing lines for Drell-Yan.
@jiuzhao originally tried to run over RAW files in a previous AProd, but they were rejected.
So, given that we will probably be rejected from running directly over RAW, and there are no relevant sprucing lines for us to use, I think we should just run over Collision23 in the case of Drell-Yan.
Ok, understood! Should we continue with !688 (merged) then? I am de-cluttering that MR as well, the way you suggested for this one.
Yes, I think let's just do with !688 (merged) and close this one. Indeed those comments apply to that MR as well - thanks!
- DrellYan_sliaison/drell_yan.py 0 → 100644
4 # This software is distributed under the terms of the GNU General Public # 5 # Licence version 3 (GPL Version 3), copied verbatim in the file "COPYING". # 6 # # 7 # In applying this licence, CERN does not waive the privileges and immunities # 8 # granted to it by virtue of its status as an Intergovernmental Organization # 9 # or submit itself to any jurisdiction. # 10 ############################################################################### 11 12 from DrellYan_sliaison.tupling_funcs_data import ( 13 make_composite_variables, 14 make_basic_variables, 15 make_hlt_event_variables, 16 make_track_variables, 17 Funtuple_with_filter, 18 make_neutral_variables, 19 ) - DrellYan_sliaison/tupling_funcs_data.py 0 → 100644
31 from DaVinci.algorithms import create_lines_filter 32 from PyConf.reading import ( 33 get_pvs, 34 get_pvs_v1, 35 get_particles, 36 get_rec_summary, 37 get_charged_protoparticles, 38 get_neutral_protoparticles,) 39 #### 40 41 metainfo_repos.global_bind(extra_central_tags=['commissioning']) 42 43 Hlt1_decisions = [ 44 'Hlt1TrackMVADecision', 'Hlt1TwoTrackMVADecision', 45 'Hlt1SingleHighPtMuonDecision','Hlt1DiMuonHighMassDecision', 46 'Hlt1TrackMuonMVADecision' One difference I spot between here and !688 (merged) is that
Hlt1DiMuonDrellYanDecision
is missing from the list here, but present in !688 (merged). I guess you want to have it.
Closing this one now !688 (merged) is submitted, following discussion above.