Automate beam energy configurations
Briefly, what does this PR introduce?
Aiming to address https://github.com/eic/EICrecon/issues/1899 by automatically adding xml configurations for all beam energy combinations to detector setups which include far_forward or far_backward subsystems.
Also changes the default energy from 18x275 to 5x41 when no values are provided.
Some of the yml files probably don't need the far detector subsystems for the studies they are used for so could be removed.
What kind of change does this PR introduce?
- [x] Bug fix (issue #__)
- [ ] New feature (issue #__)
- [ ] Documentation update
- [ ] Other: __
Please check if this PR fulfills the following:
- [ ] Tests for the changes have been added
- [ ] Documentation has been added / updated
- [ ] Changes have been communicated to collaborators
Does this PR introduce breaking changes? What changes might users need to make to their code?
No
Does this PR change default behavior?
Adds a lot more xml files to confuse the users.
We run some ci for every configuration and I think it may be based on the files in configurations/. Does that still work and does it blow up the CI load?
@simonge @rahmans1 Can we work on reconciling this PR with the changes in main? It seems in particular that there are a number of failing tests due to not having beam energy configurations in the geometry that is being tested.