-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CICE C-grid runs using 0.25deg #230
Comments
I reported the shortage of info in the stack trace here: ACCESS-NRI/ACCESS-OM3#13 |
I will set the DT_THERM back to 1350s and try again :) |
With DT_THERM set to the default, the Bgrid configuration is still running (almost 2 years). With the Cgrid (https://github.com/ACCESS-NRI/access-om3-configs/compare/34e2136cab181fd38068d9e35bbc85f3f9de9db9...anton-seaice:MOM6-CICE6:dev-025deg_jra55do_ryf-cgrid?expand=1), I get the errors with The errors are :
and
It doesn't say which extreme sfc_state detected is causing the issue, but presumably SSH. There is a bit of a "shelf?" in the crash location (a nameless bay, western bering sea): But nothing else obvious going on - I looked at daily mean of SSH, and sea-ice concentration. I can't see how turning on C-grid in CICE has impacted this ? Should I turn on time-step output for SSH and re-run (or is |
|
From the messages it looks like the error might originate in the barotropic solver, so you could try reducing the magnitude of |
Following recent discussions , I ran the 025deg ryf with
Diabatic_first=True
Dt_therm = 5400s (1.5 hours)
and otherwise the default configuration (the om2 grid / bathymetry / initial conditions / cice b-grid)
It ran until the 18th March in the second year
And crashed with too many truncations :
Is this consistent with your work @minghangli-uni - should I increase the number of allowable truncations and see if they stabilise?
Config is here: ACCESS-NRI/access-om3-configs@34e2136...51fbffa
Output is in:
/g/data/tm70/as2285/payu/dev-025deg_jra55do_ryf-bgrid/work
The text was updated successfully, but these errors were encountered: