Sprucing campaign s24c1 HLT2CALIB
Sprucing production request
Summary
Numbers are here
[Summarise the request(s), e.g. "Passthrough Sprucing (2023 MagDown) and/or "Exclusive Sprucing (2023 MagDown) for Runs ...]
(Annotated) YAML(s)
- The following template is for a single type of production. A request may contain the details for both Exclusive and Passthrough Sprucing productions "simultaneously", in which case the YAML below should be duplicated.
- Most fields are pre-filled with common or default values.
- Fields marked as {...} are required a value.
- Various fields contain helper comments (starting with "#").
- Last but not least - once finalised, the YAML(s) need(s) to be validated!
- author: {USERNAME}
name: {NAME} # E.g. "Passthrough / Exclusive Sprucing (2023 MagUp / MagDown)"
comment: {COMMENT} # E.g. "Test for first 2024 productions"
type: Sprucing
wg: DPA
inform: # Feel free to add any other relevant person
- nskidmor
- nraja
priority: 1a
input_dataset:
# 94000000 / 90000000 for Exclusive / Passthrough Sprucing
event_type: {EVENT_TYPE}
# Is there a check on consistency e.g. of magnet polarity and name?
conditions_description: Beam6800GeV-VeloOpen-MagDown-Excl-UT
conditions_dict:
configName: LHCb
configVersion: {CONFIG_VERSION} # E.g. "Collision23"
inFileType: RAW
inProPass: Real Data
inDataQualityFlag: UNCHECKED, OK, BAD # OPG decision from Autumn 2023
inProductionID: ALL
inTCKs: ALL
steps: # There are 2 steps
- name: {MOORE_STEP_NAME} # Ensure some relation to "name" given above, e.g. "Passthrough Sprucing"
processing_pass: {MOORE_PROCESSING_PASS} # E.g. "Sprucing_test_23_01"
visible: true
application:
name: Moore
version: {MOORE_VERSION}
data_pkgs: []
options:
entrypoint: {ENTRY_POINT} # E.g. Hlt2Conf.Sprucing_production:pass_spruce_production
extra_options:
input_process: Hlt2
process: Spruce
input_type : RAW
input_raw_format : 0.5
data_type : Upgrade
simulation : False
geometry_version: trunk
conditions_version: master
output_type : ROOT
compression: ZSTD:1
input:
- type: MDF
visible: true
output: # IMPORTANT: some types may only be relevant for Exclusive / Passthrough. This needs a careful check!
- type: ["B2CC.DST", "B2OC.DST", "BANDQ.DST", "BNOC.DST", "CHARM.DST", "QEE.DST", "RD.DST", "SL.DST"]
visible: false
- name: {MERGE_STEP_NAME} # Ensure some relation to "name" in step above, e.g. "Pass_merge_2023_01"
processing_pass: {MERGE_PROCESSING_PASS} # E.g. "PassMerge23_01"
visible: false
application:
name: LHCb
version: {LHCB_VERSION_FOR_CHOOSEN_MOORE_VERSION}
data_pkgs: []
options:
entrypoint: GaudiConf.mergeDST:dst
extra_options:
input_process: Hlt2
input_type : ROOT
input_raw_format : 0.5
data_type : Upgrade
simulation : False
geometry_version: trunk
conditions_version: master
output_type : ROOT
compression: ZSTD:1
input: # Should match the "output" list of the Moore step above!
- type: ["B2CC.DST", "B2OC.DST", "BANDQ.DST", "BNOC.DST", "CHARM.DST", "QEE.DST", "RD.DST", "SL.DST"]
visible: false
output:
- type: ["B2CC.DST", "B2OC.DST", "BANDQ.DST", "BNOC.DST", "CHARM.DST", "QEE.DST", "RD.DST", "SL.DST"]
visible: true