-
Notifications
You must be signed in to change notification settings - Fork 23
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
Incorrect initial conditions for most configurations #39
Comments
I'm guessing that there could be problems with the other resolutions too. |
I'd imagine so. |
@aidanheerdegen do you know if this is still the case? If so, do you know where the correct files are? |
This is a problem for all the input directories other than
So the release candidates The standard configs currently use these:
So we need to fix most of these, i.e. fix the release candidate and link to that when it's ready. Following #159 we are back to using Details for reference:
but all the others differ, including the release candidate At 0.25 deg:
but all the others differ, including the release candidate At 0.1deg:
all files differ, including the release candidate |
Also, we are now using conservative temperature as the prognostic variable for all configurations, but the initial condition is potential temperature. Is this cause for concern? Or unavoidable? |
The release candidates
I hope these are the correct files - @aidanheerdegen can you confirm? |
Yes they are the WOA initial conditions files I created. |
Is this still an issue? |
closing - fixed in |
For future reference: The GMD2020 1deg and 0.25deg configurations The GMD2020 0.1deg config |
The
input/mom_1deg/ocean_temp_salt.res.nc
file is the old Levitus initial conditions.Now we're using the regridded WOA13 files here:
Andy has an earlier version of this file, so though his md5sum is not the same, I have checked and the data inside matches.
I'm assuming all the other initial conditions files need to change also
The text was updated successfully, but these errors were encountered: