Skip to content

[RTA/DPA BW Tests] Make the config file configurable

Luke Grazette requested to merge lugrazet-make-config-configurable into master

Issue

Currently if one wants to run the BW Tests from a release, we are fixed with the input samples at that time, and would need to build at least Moore to redirect the configuration via editing benchmark_scripts/Moore_hlt2_bandwidth.sh or edit the input configuration directly ourselves under test/options/bandwidth/hlt2_bandwidth_input_2024.yaml

However it's seeming that we may want to run such tests over Data somewhat more frequently

Proposal

OVERRIDE_CONFIG_PATH, ovewrites the default configuration used in the Moore selection job. 
  Default=function of the kwargs

An environment variable overriding the input_config file (and if un-initialised, continue with our usual configuration file). Thus it becomes trivial to process Runs using lb-run or the Hlt2 stacks in the Online environment etc. like so:

Moore/run env OVERRIDE_CONFIG_PATH="<path_to_config>" DBASE/...

I propose an environment variable rather than an extra argument, because this is the least intrusive way of providing information to Moore_bandwidth_test.sh that I can think of.

ToDo:

  • Test via Moore MR (expect no change)
  • Test locally
  • Review
Edited by Luke Grazette

Merge request reports