-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add more sea ice variables #1061
Comments
|
@travissluka, as I'm plugging away on the coding front, I'm realizing that what I'm doing is very UFS/CICE-centric, and it's adding quite a bit of clunky Fortran to the already clunky IO module. Are we okay with that approach, or should we assume that the background files should be reformatted before being read by SOCA? The latter would require only minimal code changes to allow for a sea ice level dimension at the expense of extra IO. |
I would rather not have to do extra I/O, so, yes, continue adding it into SOCA. One request I have: I unfortunately think its a good time to take a look at the variable naming convention, since we're adding in new variables. Otherwise, we'll have to go back later and rename everything whenever I finally get around to talking to ALGO about what our variables should be renamed to. I'll find the CCPP spreadsheet and talk to ALGO about how these things with "categories" should be named |
Description
I'm planning to add the following to the
soca
State
. The fields will be read from a typical CICE6 history output:The 2D variables can be read by simply changing the
field_metadata
yaml, that should be straight forward (this is what we currently do in the gdas implementation of soca).The 3D seaice dynamic will require some coding on the io side since the categorical variables will have to be considered as separate variables (aice_1, aice_2, ...)
The 4D seaice thermo variables will be treated as the 3D ones by removing the category dimension.
This should help the cleanup and debugging of the
Soca2Cice
variable change as well as the AI based balance.The text was updated successfully, but these errors were encountered: