Add test of snapshot capability
What is the feature/what would you like to discuss?
@adamrher noticed that we don't have any testing in place for snapshots. We may want to add snapshots to an existing 9-timestep test. One of the possible future points of failure is that the snapshots are capped at 250 pbuf variables, so the test that the snapshot is added to should probably be one that includes CLUBB.
Possible option: ERP_Ln9_Vnuopc.ne5pg3_ne5pg3_mg37.QPC6.izumi_nag.cam-outfrq9s_clubbmf
Is there anyone in particular you want to be part of this conversation?
No response
Will this change (regression test) answers?
No
Will you be implementing this enhancement yourself?
Any CAM SE can do this
I'd say use ne3pg3_ne3pg3_mg37 instead.
Some relevant info -- I've been running ERP tests with snapshot on. The snapshot files cause the restart test to fail. For some reason the variables in the snapshot files are different in the restart run from the control run. Whereas the h0 and restart files are bfb the same as the control. Hence, turning off snapshot, the restart test passes.
Some relevant info -- I've been running ERP tests with snapshot on. The snapshot files cause the restart test to fail. For some reason the variables in the snapshot files are different in the restart run from the control run. Whereas the h0 and restart files are bfb the same as the control. Hence, turning off snapshot, the restart test passes.
@adamrher - I believe the problem exists solely in your CLUBB-MF branch. I was able to duplicate that the ERP test was not BFB when I ran with your source code. When I made an indentical test using cam6_3_116 and your outfrq9s_clubbmf use case, the run indicated the files were BFB. My jcam6_3_116 run can be seen at: /glade/scratch/cacraig/ERP_Ln9_Vnuopc.ne3pg3_ne3pg3_mg37.FHIST.cheyenne_intel.cam-outfrq9s_clubbmf.20230803_155918_a0yvs
We need to make sure this test writes out a few aerosol products to ensure that future aerosol changes do not break this.