-
Notifications
You must be signed in to change notification settings - Fork 42
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
My Bering Sea coupled ice-ocean runs don't reproduce #190
Comments
Obviously something unfortunate has crept into the code somewhere. What versions of MOM6 and SIS2 are you using, and do you have the versions of the MOM6 and SIS2 code that did reproduce across successive runs? |
I went back to some older codes and had to edit my MOM_input to get things to reproduce. Still, the current code with the updated MOM_input gets me back to the trouble again. The change I made to MOM_input is to go back to the original OBC where the entire domain has open boundaries, including all of the land masks. The weird thing is my Arctic does reproduce from one run to the next and I've tried to make the Bering as close to it as possible! |
It wasn't SIS2 or MOM6 versions changing, it was the change to FMS2 that introduced the oddity. With FMS2 I got two consecutive runs to match, but not the third, just random. When compiled for debugging, things do reproduce. I noted at the top of the thread that the diffs are coming in via the wind stress. Note that going to FMS2 implies new versions of the coupler, atmos_null, land_null, and maybe ice_params as well. |
AFAIK we are still using FMS1 interpolation operations in the FMS2 infra layer, so I'd say its more likely to be coming from the other components. |
If I add a print statement (I know, I know) to set_wind_stresses_C, I recover the old FMS1 answer. This is with gfortran 8.3.0. gfortran 11.3.0 compiling with FMS1 gives this:
|
Add |
My Bering Sea runs now get different stats result for each run, it seems. The differences creep in through " u/v WindStr_[xy] before SIS_C_dynamics" and then "str_d/str_t/str_s in SIS_C_dynamics".
This is followed by pages of stuff like:
This didn't used to be the case, but it has been nagging me for over a month now.
The text was updated successfully, but these errors were encountered: