ISISComputingGroup / ISISComputingGroup/IBEX
NICOS scripts checkpoint during running and restart automatically
- Dominant language
- No language data
- Stars
- 6
- Forks
- 2
- Avg merge
- 16h 40m
- Merged PRs (30d)
- 2
Description
As an ISIS user, I am keen not to lose beam time because there has been a hardware crash or mains blip on part of the control system (probably the computer). As I would expect the control system to restart under these conditions to log what happens to my science, even if it is bad. I would also like my scripts - which are usually waiting for a particular condition or time period - to restart from an automatic checkpoint and continue the experiment from where it was interrupted if at all possible. Much of the time this would be likely to save my data and beam-time. I would see this as a selling point of the new EPICS system because the existing SECI system does not provide restart-able scripts.
Notes:
=====
1) I would like defaults in the scripting system to be set for everything to be set to continue on the basis that this gives me the best chance of saving my beam time, maybe a whole nights worth of beam.
2) There are some instruments or experiments where I might need to specify that the experiment is aborted or that equipment (for example, some choppers) do not come on after a machine failure.
3) This doesn't replace the need for notification to alert me of any issues with the machine or script progress.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.