-
Notifications
You must be signed in to change notification settings - Fork 13
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 Segfault with current GEOSgcm main #336
Comments
Okay. I can fix the CICE4 failure by reverting the flags there and I'm going to work on getting that in. But we have another issue: MOM5 and MOM6 are non-zero-diff now. I've tried reverting the build flags for MOM5 and MOM6 to the old flags as well but that doesn't make them zero-diff. So, I'm thinking this might be due to Intel 2021.2. If so...not much I can do. |
Note: MOM5 and MOM6 are zero-diff with 1moment, just not 2moment. Thus I must assume this is the 2moment issue like we saw in MAPL: GEOS-ESM/MAPL#762 Not sure what triggered it, but I think day of the week can trigger non-zero-diff with 2moment it seems. |
Matt, thanks you are looking into this. For coupled model we are trying to run different microphysics in feature/aogcm branch by the way, it may have different problems. |
Eeep! Well, we shall see when we get to it! |
There seems to be a problem with GEOSgcm and CICE4 at the moment. After the latest rounds of updates to GEOSgcm, I am now seeing a segfault with CICE4 in both MOM5 and MOM6 runs. Both point to the same line (truncated traceback):
Now, as far as I can tell, CICE4 hasn't changed in a long time, so this is probably on me. Two things have changed that I am suspecting:
I'm going to try undoing #2 in CICE4. That's my best bet.
CC @sanAkel @yvikhlya @zhaobin74
The text was updated successfully, but these errors were encountered: