You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In current s2s CMEPS restart regression test, the reproducibility is achieved when oro data does not contain the lake frac and lake depth record, therefore lake points won't be differentiated from ocean points in the oceanfrac in fv3, so lake temperature will have the issue of taking ocean points temperature. In this ticket, the oro data is updated with lake fract and lake depth, the restart reproducibility issue will be fixed.
The text was updated successfully, but these errors were encountered:
I have tested the restart repro at c384 using our sandbox on cheyenne. I obtained from Shan the updated c384 input data for 20120101 (oro, sfc_data and gfs_data). I updated FV3 (def9be1) so it can accept a single input_nml variable frac_grid true or false. The oro_data does contain both lake_frac and lake_depth.
Running with frac_grid=F, I obtain the same 7 fields in FV3 differing on restart as noted here: #34 (comment)
In current s2s CMEPS restart regression test, the reproducibility is achieved when oro data does not contain the lake frac and lake depth record, therefore lake points won't be differentiated from ocean points in the oceanfrac in fv3, so lake temperature will have the issue of taking ocean points temperature. In this ticket, the oro data is updated with lake fract and lake depth, the restart reproducibility issue will be fixed.
The text was updated successfully, but these errors were encountered: