@rjhunter, with the planned MR to allow data-processing with these tests (instead of needing to be independently hacked by whoever wants to use it), might be useful to sneak in this too?
From the discussion in that MR and then mattermost it seems this should be postponed until we have 2024.Q1.2 MC (rather than expected-24 MC) as input samples.
After !433 (merged) we'll move to using data by default which uses the appropriate geometry_version and conditions_version.
We don't currently plan to have an MC test as well with 2024.Q1.2 MC at the moment. However, if we were to add one, it would be possible after that MR to use it with a DD4HEP stack and provide the above options in the configuration yaml.
I think therefore we can close this one when the above MR goes in. Whilst it'd be nice to see the bandwidth tests run over MC with a DD4HEP stack, I don't think it is necessary and therefore warrants keeping this issue open until we (maybe) try that. WDYT?