Automatically configuring for Analysis Productions
When submitting Run 1 and Run 2 Analysis Productions most people take advantage of the automatically_configure: true
option.
This removes the need for people to handle information relating to input data and makes people's options files much more consise.
It works by generating a Python file like this one which is prepended to the list of options files provided by the user:
Click to see examples
from Configurables import DaVinci
try:
DaVinci().Turbo = False
except AttributeError:
# Older DaVinci versions don't support Turbo at all
pass
DaVinci().RootInTES = '/Event/Bhadron'
DaVinci().InputType = 'MDST'
DaVinci().DataType = '2015'
DaVinci().Simulation = False
DaVinci().Lumi = True
from Configurables import CondDB
CondDB(LatestGlobalTagByDataType=DaVinci().DataType)
from Configurables import DaVinci
try:
DaVinci().Turbo = False
except AttributeError:
# Older DaVinci versions don't support Turbo at all
pass
DaVinci().RootInTES = '/Event/AllStreams'
DaVinci().InputType = 'MDST'
DaVinci().DataType = '2018'
DaVinci().Simulation = True
DaVinci().Lumi = False
DaVinci().DDDBtag = 'dddb-20170721-3'
DaVinci().CondDBtag = 'sim-20190430-vc-mu100'
For Run 3 this option hasn't yet been implemented as it wasn't clear what should be done however we're now approching a state where it might start to be reasonable.
The mechanism for doing this in Run 3 was designed into lbexec
and the extra_options
parameter that people have been using when submitting productions. For example:
extra_options:
input_type: ROOT
input_process: "TurboPass"
input_stream: "bandq"
input_raw_format: 0.5
simulation: False
data_type: "Upgrade"
geometry_version: trunk
conditions_version: master
I'm opening this issue to start the discussion around what we need to implement to be able to make this work robustly for 2024.
In general I think we should favour setting the defaults in the physics application itself if we can (possibly via the new FSRs).