Re-Processing of 2016 pHe data
Take as a model the reco16Smog step:
Likely we may as well just stage all the needed runs to begin with, and then limit testing to 50k events or something. Runs for staging are: [174618, 175302] (8 TeV)
Previous testing procedure is : lb-dirac dirac-production-request-run-local -c x86_64_v2-centos7-gcc62-opt test.yml 'Reprocess_2016pHe' --input-files='/lhcb/LHCb/Collision16/RDST/00051630/0004/00051630_00040513_1.rdst'
. Not sure if we need to change the platform for Brunel
, and what is the input files (Are they RAW
s?)
Need input on lots of the details below:
- author: ngrieser
name: Reco16Smog # E.g. "Passthrough / Exclusive Sprucing (2023 MagUp / MagDown)"
comment: 2024 re-processing of pHe # E.g. "Test for first 2024 productions"
type: ??? #Reconstruction
wg: DPA
inform: # Feel free to add any other relevant person
- ngrieser
- samarian
- chlucare
- ggrazian
priority: 1a
input_dataset:
# 94000000 / 90000000 for Exclusive / Passthrough Sprucing
event_type: 90000000
# Is there a check on consistency e.g. of magnet polarity and name?
conditions_description: ?? #Beam6500GeV-VeloClosed-MagDown
conditions_dict:
configName: LHCb
configVersion: Collision18 #I think it should be Protonhelium16 E.g. "Collision23"
inFileType: RDST #I think it should be RAW
inProPass: Real Data/?? #I think Real Data is sufficient
inDataQualityFlag: OK # To be checked if also UNCHECKED is good
inProductionID: ALL
inTCKs: ALL
steps: # There are 2 steps
- name: Reprocess_2016pHe # Ensure some relation to "name" given above, e.g. "Passthrough Sprucing"
processing_pass: Reco16Smog # E.g. "Sprucing_test_23_01"
visible: true
application: Brunel/v55r4
data_pkgs:
- AppConfig.v3rXXXX
options:
- $APPCONFIGOPTS/Brunel/DataType-2016.py
- $APPCONFIGOPTS/Brunel/PVreco-smog2016.py
- $APPCONFIGOPTS/Brunel/Brunel-betaLoop.py
options_format: ??
dbtags:
DDDB: dddb-20150724
CondDB: cond-20160522
input:
- type: RDST #It should be RAW
visible: true
output: # IMPORTANT: some types may only be relevant for Exclusive / Passthrough. This needs a careful check!
- type: [BHADRON.MDST, BHADRONCOMPLETEEVENT.DST, CHARMCOMPLETEEVENT.DST, CHARM.MDST, DIMUON.DST, EW.DST, LEPTONIC.MDST, SEMILEPTONIC.DST] ???? #Could it be FULL.DST?
visible: true
Edited by Chiara Lucarelli