Introduce diagnostic variables for CABLE outputs#688
Conversation
799344b to
43c565b
Compare
7edfb5a to
d9d1179
Compare
d9d1179 to
80390f7
Compare
|
Bitwise comparisons have been tested manually with the following script, allowing for an absolute tolerance of #!/bin/bash
module load nccmp
set -ex
for f in runs/fluxsite/outputs/*R0*.nc; do
nccmp -d -x Rnet -x RadT ${f/R0/R0} ${f/R0/R1}
nccmp -d -v Rnet -v RadT -t 1e-3 ${f/R0/R0} ${f/R0/R1}
doneOutput: |
|
Hi @Whyborn, do you mind taking a look at the new diagnostic variables being added in this PR? I'm wary that changing the core data structures could impact the coupled model? |
|
I'll have a proper look at it when I get back on Thursday |
Whyborn
left a comment
There was a problem hiding this comment.
Looks good to me, just that question about air%rlam. Should we just remove that everywhere now?
Possibly, although I think I'll leave that for a separate PR. The replacement of |
This change introduces diagnostic variables for CABLE outputs to compute various diagnostics outside the output module. This is required to bring in the new parallel I/O output module (#655), where output fields are associated with a pointer to an array which is written.
Type of change
Please delete options that are not relevant.
Checklist
Testing
Outputs contain precision level differences in variables
RnetandRadTdue to round off errors in the calculation of the diagnostic. All other variables are bitwise compatible.📚 Documentation preview 📚: https://cable--688.org.readthedocs.build/en/688/