-
Notifications
You must be signed in to change notification settings - Fork 7
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
Switching to Symmetric MOM6 #255
Comments
This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there: https://forum.access-hive.org.au/t/cosima-twg-meeting-minutes-2025/4067/2 |
I built with mom_symmetric and the normal repro test passes. . In my view that is enough to make the change ? |
Agreed and good timing! |
Yay - it only impacts the deployment, so ill put the change in deployment repo (probably ACCESS-NRI/ACCESS-OM3#33) |
Yeah, makes sense. I just noticed that it's already there, though isn't it? Here, specifically. |
Yes - I was predicting the future there ;-) |
Regional MOM6 needs to run on a symmetrical executable whilst access-om3 is running on a non-symmetrical executable. Switching access-om3 to symmetrical will reduce the number of executables that need to be supported.
The difference between symmetric and non-symmetric mom6 is that there is some overlap of grid cells on adjacent tiles. This uses a very small amount of extra memory but may make some gradient calculations easier. The central version of MOM6 runs tests to ensure that switching between symmetrical on non-symmetrical does not change the model solution but we may need to test on the access-om3 models to ensure that this is still the case with our parameterisations.
The suggestion is that we should compare a test case of access-om3 run in symmetrical and non-symmetrical mode to check that there are no issues before switching over
The text was updated successfully, but these errors were encountered: