2023 Re-Stripping Campaign -- 2018 (S34r0p3)

Stripping production request -- WIP

Summary

Preparation of yaml is on-going

For testing locally, we need staged some samples:

Run range: 216353 (MU), 213673 (MD)

YAML(s)

- author: ngrieser
  name: Stripping34r0p3_MD  # E.g. "Passthrough / Exclusive Sprucing (2023 MagUp / MagDown)"
  comment: 2023 incremental restripping of 2018 MD data # E.g. "Test for first 2024 productions"
  type: Stripping

  wg: DPA
  inform:  # Feel free to add any other relevant person
  - ngrieser
  - avenkate
  - fredi
  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  # E.g. "Collision23"
      inFileType: RDST
      inProPass: Real Data/Reco18
      inDataQualityFlag: OK  # To be changed as soon as DQ is fully in place
      inProductionID: ALL
      inTCKs: ALL

  steps:  # There are 2 steps
  - name: Stripping34r0p3_md  # Ensure some relation to "name" given above, e.g. "Passthrough Sprucing"
    processing_pass: Stripping34r0p3  # E.g. "Sprucing_test_23_01"
    visible: true
    application: DaVinci/v44r11p6
    data_pkgs:
    - AppConfig.v3r421
    - TMVAWeights.v1r18
    - Det/SQLDDDB.v7r12
    options:
    - $APPCONFIGOPTS/DaVinci/DV-Stripping34r0p3-Stripping.py
    - $APPCONFIGOPTS/DaVinci/DataType-2018.py
    - $APPCONFIGOPTS/DaVinci/InputType-RDST.py
    - $APPCONFIGOPTS/DaVinci/DV-RawEventJuggler-0_3-to-4_3.py
    - $APPCONFIGOPTS/Persistency/Compression-ZLIB-1.py
    options_format: Stripping
    dbtags:
      DDDB: dddb-20220927-2018
      CondDB: cond-20200921
    input:
    - type: RDST
      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]
      visible: false
  - name: Merge_Stripping34r0p3_md  # Ensure some relation to "name" in step above, e.g. "Pass_merge_2023_01"
    processing_pass: Merge_Stripping34r0p3  # E.g. "PassMerge23_01"
    visible: false
    application: DaVinci/v44r11p6
    data_pkgs:
    - AppConfig.v3r421
    - TMVAWeights.v1r18
    - Det/SQLDDDB.v7r12
    options:
    - $APPCONFIGOPTS/Merging/DV-Stripping-Merging.py
    - $APPCONFIGOPTS/Persistency/Compression-LZMA-4.py
    options_format: Merge
    dbtags:
      DDDB: dddb-20220927-2018
      CondDB: cond-20200921
    input:  # Should match the "output" list of the DV step above!
    - type: [BHADRON.MDST, BHADRONCOMPLETEEVENT.DST, CHARMCOMPLETEEVENT.DST, CHARM.MDST, DIMUON.DST, EW.DST, LEPTONIC.MDST, SEMILEPTONIC.DST]
      visible: false
    output:
    - type: [BHADRON.MDST, BHADRONCOMPLETEEVENT.DST, CHARMCOMPLETEEVENT.DST, CHARM.MDST, DIMUON.DST, EW.DST, LEPTONIC.MDST, SEMILEPTONIC.DST]
      visible: true

- author: ngrieser
  name: Stripping34r0p3_MU  # E.g. "Passthrough / Exclusive Sprucing (2023 MagUp / MagDown)"
  comment: 2023 incremental restripping of 2018 MU data # E.g. "Test for first 2024 productions"
  type: Stripping

  wg: DPA
  inform:  # Feel free to add any other relevant person
  - ngrieser
  - avenkate
  - fredi
  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-MagUp
    conditions_dict:
      configName: LHCb
      configVersion: Collision18  # E.g. "Collision23"
      inFileType: RDST
      inProPass: Real Data/Reco18
      inDataQualityFlag: OK  # To be changed as soon as DQ is fully in place
      inProductionID: ALL
      inTCKs: ALL

  steps:  # There are 2 steps
  - name: Stripping34r0p3_mu  # Ensure some relation to "name" given above, e.g. "Passthrough Sprucing"
    processing_pass: Stripping34r0p3  # E.g. "Sprucing_test_23_01"
    visible: true
    application: DaVinci/v44r11p6
    data_pkgs:
    - AppConfig.v3r421
    - TMVAWeights.v1r18
    - Det/SQLDDDB.v7r12
    options:
    - $APPCONFIGOPTS/DaVinci/DV-Stripping34r0p3-Stripping.py
    - $APPCONFIGOPTS/DaVinci/DataType-2018.py
    - $APPCONFIGOPTS/DaVinci/InputType-RDST.py
    - $APPCONFIGOPTS/DaVinci/DV-RawEventJuggler-0_3-to-4_3.py
    - $APPCONFIGOPTS/Persistency/Compression-ZLIB-1.py
    options_format: Stripping
    dbtags:
      DDDB: dddb-20220927-2018
      CondDB: cond-20200921
    input:
    - type: RDST
      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]
      visible: false
  - name: Merge_Stripping34r0p3_mu  # Ensure some relation to "name" in step above, e.g. "Pass_merge_2023_01"
    processing_pass: Merge_Stripping34r0p3  # E.g. "PassMerge23_01"
    visible: false
    application: DaVinci/v44r11p6
    data_pkgs:
    - AppConfig.v3r421
    - TMVAWeights.v1r18
    - Det/SQLDDDB.v7r12
    options:
    - $APPCONFIGOPTS/Merging/DV-Stripping-Merging.py
    - $APPCONFIGOPTS/Persistency/Compression-LZMA-4.py
    options_format: Merge
    dbtags:
      DDDB: dddb-20220927-2018
      CondDB: cond-20200921
    input:  # Should match the "output" list of the DV step above!
    - type: [BHADRON.MDST, BHADRONCOMPLETEEVENT.DST, CHARMCOMPLETEEVENT.DST, CHARM.MDST, DIMUON.DST, EW.DST, LEPTONIC.MDST, SEMILEPTONIC.DST]
      visible: false
    output:
    - type: [BHADRON.MDST, BHADRONCOMPLETEEVENT.DST, CHARMCOMPLETEEVENT.DST, CHARM.MDST, DIMUON.DST, EW.DST, LEPTONIC.MDST, SEMILEPTONIC.DST]
      visible: true