Would it make sense to have GARD clobber existing output files? I recently ran a GARD simulation that took 4.5 hours, just to have it error when the simulation went to write the output...
---------------------------------------------------
Time profiling information
---------------------------------------------------
Total Time : 593774 s (CPU time)
Total Time : 16489 s (wall clock)
---------------------------------------------------
Allocation : 0 %
Data Init : 0 %
GeoInterp : 0 %
Transform : 0 %
Analog : 20 %
Regression : 3 %
Log.Regres : 77 %
Log.Analog : 0 %
---------------------------------------------------
Parallelization overhead
Residual : 0 %
---------------------------------------------------
==========================================
Writing output
NetCDF: String match to name in use
/gpfs/flash/jhamman/GARD_downscaling_20190423/NCAR_WRF_50km/analog_regression_3/19510101-19821231/gard_output.analog_regression_3.NCAR_WRF_50km.noresm.hist.19510101-19821231.pcp.nc:pcp
Perhaps there are actually two options here. 1) GARD should error error early if an output file already exists or 2) GARD should clobber the existing output file.
@gutmann - thoughts on how this should be handled?
Would it make sense to have GARD clobber existing output files? I recently ran a GARD simulation that took 4.5 hours, just to have it error when the simulation went to write the output...
Perhaps there are actually two options here. 1) GARD should error error early if an output file already exists or 2) GARD should clobber the existing output file.
@gutmann - thoughts on how this should be handled?