Restarting a job overwrites the existing output file
Issue #44
resolved
Care has to be taken when restarting as the new output will be written to a file matching the existing output and hence we clobber the original data. Ideally we would simply append to the existing data (but there are common cases where we do want to clobber, i.e. when rerunning a case but not restarting).
This is probably something to be considered as a part of a longer term/large scale look at addressing all of our I/O.
Comments (3)
-
reporter -
reporter Fixed in release 8.1
-
reporter - changed status to resolved
Fixed in 8.1
- Log in to comment
In new diagnostics there is an append_old flag (https://gyrokinetics.gitlab.io/gs2/page/namelists/index.html#gs2_diagnostics_knobs-append_old) which ensures we expand the existing file rather than clobbering it. PR #314 starts to add this feature for the old diagnostics as well.
We could perhaps consider if it’s possible to try giving this a smart default (true if our init option indicates that we are restarting).