-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update array sizes used in YOG parameterisation #50
Conversation
…ces of CAM variables to other subroutines, and use assumed shape everywhere possible.
Previous version of YOG runniing f09 aquaplanet by @MarionBWeinzierl 3 Jan 0900 ![]() YOGDQ at 912 hPa: ![]() |
This branch of YOG runniing f09 aquaplanet by @jatkinson1000 3 Jan 0900 ![]() 820 hPa ![]() YOGDQ at 912 hPa ![]() |
Next look to do a 100 day run with the settings Paul sent. |
1edeea4
to
d80beae
Compare
Everything fine with that run? |
So, given that this is clearly better than it was previously I was thinking we should merge now to provide everyone access to this fix from the main Or would you prefer to do the run from here first? |
d80beae
to
52c0834
Compare
My resolve #47
Due to the way CAM uses part-full chunks to pass arrays (
ncol
<=pcol
) the assumed sizes in YOG may not be consistent with sizes passed in from a cam state variable.This has been gone through with some checks made.