ISISComputingGroup / ISISComputingGroup/IBEX
INFRASTRUCTURE: Rationalise the end of run scripts
- Dominant language
- No language data
- Stars
- 6
- Forks
- 2
- Avg merge
- 16h 40m
- Merged PRs (30d)
- 2
Description
As a developer I want the script that is run when a run ends to be a single script under the IBEX project so that it can be updated and released reliably. These should be configured using a configuration script. Currently the script on different instruments may be completely custom so this ticket is to distil these scripts into a single script and configuration file. The initial work and explanation should have been created as part of #6175.
### Acceptance Criteria
- There is a single set of end of run scripts
- All instruments have the necessary configuration file to run these
- Optional (decide in planning): current instruments are modified to use the new scripts
### Acceptance Criteria
- End of run scripts requirements are found adn written down by looking at all instrument end of run scripts (found in the standard user documents folder in Configurations), called:
- end_of_run.cmd
- end_of_autosave.cmd
- end_of_crpt_snapshot.cmd
- end_of_store.cmd
- new end of run script is written
- script is set to run at end of run
-
### Notes
Script is different on different machine but should be made more similar on all machines.
Script should no longer live in documents but in the ibex system somewhere
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.