Currently the simulation works only on 2016 conditions. There is a place where the user can define the runYear of the data they want to simulate. Unfortunately the corresponding run conditions to these years, other than 2016, have not been defined.
Most likely this would be done by going through datasets on the opendata.cern.ch portal and looking at their production scripts, what options does the cmsDriver commands have there as the run conditions and beamspots for each step of the simulation.
In the file run-pp-simulation.yaml:
script:
image: python:3.11-slim
command: [python]
source: |
import json, os
ALL_CONDS = {"2016": {"conditionsGenSimReco": "106X_mcRun2_asymptotic_v13", "conditionsDigiPatNano": "106X_mcRun2_asymptotic_v17", "conditionsHLT": "80X_mcRun2_asymptotic_2016_TrancheIV_v6", "beamspot": "Realistic25ns13TeV2016Collision"},
"2015": {"conditionsGenSimReco": "106X_mcRun2_asymptotic_v13", "conditionsDigiPatNano": "106X_mcRun2_asymptotic_v17", "conditionsHLT": "80X_mcRun2_asymptotic_2016_TrancheIV_v6", "beamspot": "Realistic25ns13TeV2016Collision"}
# Add other years here
}
# To-do: 2015 is only a mock runYear in ALL_CONDS, check what are the conds for that year for real
Currently the simulation works only on 2016 conditions. There is a place where the user can define the runYear of the data they want to simulate. Unfortunately the corresponding run conditions to these years, other than 2016, have not been defined.
Most likely this would be done by going through datasets on the opendata.cern.ch portal and looking at their production scripts, what options does the cmsDriver commands have there as the run conditions and beamspots for each step of the simulation.
In the file
run-pp-simulation.yaml: