A quick PR to fix issues I ran into when I had STOP_N set to a value beyond what the snapshot file contained. I figure getting this PR in sooner rather than later will help with others' development, as mistakenly over-shooting one's snapshot file seems like an easy error for a user to make.
Fixes #160
Tests run:
Ran a "successful" fail on Cheyenne with Intel and on Izumi with NAG and PGI to ensure that the resulting errors were what should be expected. Also ran successful simulations with the same configurations, but with the proper STOP_N value.
The cases themselves were physics test bed runs with the Kessler physics suite. The snapshot files used to force the null dycore can be found on cheyenne here:
A quick PR to fix issues I ran into when I had
STOP_Nset to a value beyond what the snapshot file contained. I figure getting this PR in sooner rather than later will help with others' development, as mistakenly over-shooting one's snapshot file seems like an easy error for a user to make.Fixes #160
Tests run:
Ran a "successful" fail on Cheyenne with Intel and on Izumi with NAG and PGI to ensure that the resulting errors were what should be expected. Also ran successful simulations with the same configurations, but with the proper
STOP_Nvalue.The cases themselves were physics test bed runs with the Kessler physics suite. The snapshot files used to force the null dycore can be found on cheyenne here:
/glade/work/nusbaume/SE_projects/new_cam_sandbox/testing_files/kessler_snapshotand on Izumi here:
/home/nusbaume/CAM/SE_projects/new_cam_sandbox/run_files/cam_snapshot_kessler.cam.h1.0001-01-01-00000.nc