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
improve sync_output_to_gdata.sh and sync_restarts_to_gdata.sh safety #59
Comments
also |
I presume you're moving things to a similarly named directory to the current one so something like Though it's probably better to send some arguments to the script in order to do some simple sanity checking. |
You're right that this isn't a great solution, more of a hack that has propagated. I would say I don't know that there is a a great way around this. I am on record (with Marshall at least if he remembers) as wanting to uniquely name outputs with |
As for the restart issue, some of this could be fixed by redoing some of the |
the commits above have added |
The trouble with |
At present
sync_output_to_gdata.sh
andsync_restarts_to_gdata.sh
rely on the user to remember to setGDATADIR
insync_output_to_gdata.sh
to a path that does not clash with anything already existing. This is dangerous: I typically start a new experiment from a previous one, and if I forget to updateGDATADIR
the previous experiment's output will (I think!) be overwritten.I can't immediately think of a safer / more foolproof way to do it.
--dry-run
,--itemize-changes
,--ignore-existing
, etcGDATADIR
and assume that the user knows to checkout a new branch for each experiment (and choose a branch name that is useable as a dir name)? - sounds even worse...The text was updated successfully, but these errors were encountered: