-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resume Run Functionality #273
Resume Run Functionality #273
Conversation
Is there a reason the NeXus file itself cannot be used as the source of information for a restarted run if the currently written to file uses the |
I considered that, but thought it would couple the design of the file format with this functionality. I'd rather avoid that if possible. |
But all the information is already recorded in the data file (and can be assumed to always be there, as it is all pretty basic information). I can't see why just using that is not the most straightforward. |
On second thoughts, you are right that this is the cleanest way to do it. |
Summary of changes
Added behaviour for the Nexus Writer to resume a run if it was interrupted by the component going down.
A file with extension ".partial_run" is added to the local path when a run_start is received. This file is removed when the nexus file is transferred to the archive (signalling a successful run).".partial_run"".nxs" files in the local path are read and runs re-created (as.partial_run.nxs files indicate that a previous instance of nexus writer had failed).Instruction for review/testing
General code review.
Tool was tested with simulated data.