[Bug]: Figure out why `TREFHT` regridded reference variable is not regridding on `main` with ESMF bilinear
Opened this issue · 0 comments
What happened?
In PR #815:
This PR validates the replication of the slice flag feature added in PR #750 to fix #759.
I re-ran
ex1.py
and found that all.nc
files produced are now within the relative tolerance.For metrics, all but one is within the relative tolerance. This single metric is related to the regridded reference data for
"TREFHT"
with theland
region. In trefht.py, I compare the.nc
file for the regridded reference data between xCDAT/xESMF and CDAT/ESMF. I found that CDAT/ESMF doesn't seem to actually regrid the data since the original and regridded reference variables are the same, as noted in this PR review comment. I think this is leading to the large diffs along the coast lines, as shown below.
xCDAT | CDAT | Diff |
---|---|---|
In PR #794, I noticed how bilinear regridding with xCDAT/xESMF produces nan location mismatches when comparing land sea masks to CDAT/ESMF. I think we should move forward for now and debug this more later on in a separate PR.
What did you expect to happen? Are there are possible answers you came across?
The reference TREFHT
variable should be regridded since the mv2.regrid
is called below:
e3sm_diags/e3sm_diags/driver/utils/general.py
Lines 246 to 254 in c8404ab
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
No response
Anything else we need to know?
No response
Environment
main
branch