-
Notifications
You must be signed in to change notification settings - Fork 12
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
diag bugs with AusCOM driver (affecting ACCESS-OM2) #61
Comments
The CICE5.1 manual p75 says:
(This is a confusing convention. My interpretation is: if a variable name doesn't end in |
In the AusCOM driver the
In some drivers the subroutine
But (as @russfiedler pointed out) Consequently (as confirmed above), these non-
This is probably also the case for these, which output the
|
In contrast, for the following diagnostics the
|
Only |
These are output only as non- |
The remaining variables that didn't go through
I'm not sure whether they will affect any diagnostics. |
I checked and confirm that BGC fluxes are identical between My question is whether they are really grid cell average or not. I ask this because Lines 467 to 470 in 2572851
This multiplication by ice area suggests that |
Just to follow up on my previous comment. |
Thanks to Stewart Allen for flagging this issue (see Slack discussion https://arccss.slack.com/archives/C6PP0GU9Y/p1627269245007400).
These diagnostics are identical in access-om2, and shouldn't be:
fresh
andfresh_ai
fsalt
andfsalt_ai
fhocn
andfhocn_ai
fswthru
andfswthru_ai
This issue probably also affects these diagnostics and their
_ai
counterparts:alvdr
,alidr
,alvdf
,alidf
,fNO
,fNH
,fN
,fSil
, but I haven't checked.I did a test run in
/home/156/aek156/payu/1deg_jra55_iaf_cice_diag_test
, which gives these test results for equality of some diagnostics and their_ai
counterparts:prints
The text was updated successfully, but these errors were encountered: