-
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
CICE Grid Areas #116
Comments
To address this warning:
we just need to rename The cice subroutine There may also be an issue with the
Edit: And similar concerns about |
Tangentially related, it looks like MOM doesn't actually use angle_dx from the supergrid, so it would be good to check if the MOM diagnostic output of this angle (possibly this would be the cos_rot, sin_rot fields?) match angle_dx. i.e. its possible we shouldn't be using those fields for the cice grid, and should be calculating it in the same way MOM does. |
Following on from #101, we found that tarea, uarea, tlat, tlon and anglet are not being loaded from the grid file, and are instead computed internally in cice.
There is this message in ice.log:
(popgrid_nc) CICE will calculate angleT, TLON and TLAT
The code and output for these look ok at first check.
For the areas, the areas internally calculated by cice (based on
htn
andhte
fields) are saved in the history output. Comparing these to the input grid, shows noteable differences probably due to CICE calculating them internally based on the assumption the grid cells are rectangular:In OM2, code was added to load the areas from the grid file.
There appears to be an option to do something similar in the cmeps driver for CICE:
Which looks like it will get the area from the mesh file.
grid_format = meshnc
is an undocumented option only in the driver, but might be a reasonable enough approach for us.The text was updated successfully, but these errors were encountered: