-
Notifications
You must be signed in to change notification settings - Fork 23
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
Make syncing of restart directories to /g/data
standard
#275
Comments
Agreed - this has been on my back burner for a while. Would need to specify two sync paths so we can store restarts somewhere different from the outputs that the cookbook syncs. |
This would also require a rethink of how the payu driver, collation and sync script interoperate.
In practice I've manually collated restarts at the conclusion of an experiment (using It is not uncommon to have collation failures in restarts and outputs, so at the end of an experiment it's a good idea to collate any uncollated files and re-sync. |
I've been meaning to make a I think it would also be easier to do this way, with access to all the important run information. |
I feel that it would be much easier if outputs and restarts were in the same folder, as they are already in the job directory archive. I've been syncing my restarts for the ERA-5 runs across to the same directory in |
An advantage to there being so many open issues on the |
Given the new scratch file expiry limits, I suggest that the
sync_data.sh
script be altered to automatically sync restarts, as well as outputs, to/g/data
to avoid losing them all if you forget to do it by hand.The text was updated successfully, but these errors were encountered: