Remove necessity to use TestFileDB in HLT2 BW tests and add new 2023 HLT2 BW test
Compare changes
FYI @sstahl @enoomen @shunan @lugrazet
Goes with Moore!2463, LHCbNightlyConf!1051 and lhcb-core/LHCbPR2HD!254 (merged).
The periodic BW tests are currently restricted to using inputs from the TestFileDB. We need flexibility to be able to run over samples not in the TestFileDB so we can quickly reconfigure these tests to use e.g. new samples from the HLT1 BW division team.
To achieve this, run_bandwidth_test_jobs
now reads a yaml file defining the input. This can either provide a testfiledb_key
(as was previously given via the cmd line) or can provide a list of input files. I chose yaml so that we can add comments and it has a nicely-formatted way to store a big list of files that can be easily read in by python. The options files live under Moore/Hlt/Hlt2Conf/tests/options/bandwdith/
and are added in Moore!2463.
I also add a new Moore_hlt2_2023_bandwidth.sh
script to configure a new test on that sample. I think I've added the necessary configuration in LHCbNightlyConf!1051 and lhcb-core/LHCbPR2HD!254 (merged) for this test to run, but not sure if more changes in other projects are required.
eos/
is very slow. Switched on by default still to not slow down the periodic tests.extra-options
to gaudirun.py
,TODO:
Moore_spruce_all_lines.sh
?