-
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
Sudden crashes with excessive SSH #55
Comments
The latest commit on the
This is at the head of the Persian Gulf. This crash seems nearly identical to the previous test (same location and date, nearly the same SSH): ACCESS-NRI/access-om3-configs#5 (comment). |
changing
|
Also crashes identically with the latest ACCESS-OM3 commit 377c1fc (unsurprising, as this just adds the GPTL timing library). |
The
|
MOM6-CICE6-WWIII configuration crashes at the same location as MOM6-CICE6 after running
|
Using more lenient checks from from mom6-om4-025 allows the MOM6-CICE6 1° run to proceed for at least 2 years with no issues. |
This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there: https://forum.access-hive.org.au/t/namelist-configuration-discussion-meeting/1917/9 |
Maybe fixing this will help? #164 |
Thanks @aekiss. I am currently experiencing crashes in the MOM6-CICE6 1 deg IAF and RYF configs (main branch) after a few months of runtime (3-4 months). Each failure appears to be due to different reasons (I have listed a few error logs below). Test experiment 1 - IAF 1deg
Test experiment 2 - RYF 1 deg
|
@ezhilsabareesh8 is this crashing even with more lenient checks? |
Thanks @aekiss. With the recent changes of setting |
The RYF 1-degree MOM6-CICE6 configuration still crashes with the above error. However, there is a significant difference between the
|
MOM6-CICE6 1° configs are crashing after running for several weeks/months. Excessively large SSH appears in less than 1 day, without unusual wind stress - see
ACCESS-NRI/access-om3-configs#5 (comment)
ACCESS-NRI/access-om3-configs#5 (comment)
The text was updated successfully, but these errors were encountered: