-
Notifications
You must be signed in to change notification settings - Fork 30
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
Difference lat-lon maps only show half for several obs datasets #711
Comments
After some troubleshooting, it ruled out change in |
Found an old cdms issue pointing out the same behavior. |
The regriding step also produce warning as follows:
It seems cdms is not properly built with esmf. Not sure if this is relevant to the regriding issue here. |
@chengzhuzhang, I'm going to see if conda-forge/cdms2-feedstock#87 fixes this. I patched the imports in cdms2 to hopefully bring in |
@xylar I'm glad to report: your fix conda-forge/cdms2-feedstock#87 works, and thanks for adding a check for testing conda-forge/cdms2-feedstock#89. |
@chengzhuzhang, could you add a test somewhere in E3SM diags where you test for
but you might want to have a Such an error would tell us right away that there's a problem, rather than noticing it only when plots are half missing. |
Great suggestion. I think it makes sense to add it as one of the CI/CD tests. |
Fixed. |
In v2.9.0rc2, several lat-lon maps (bottom figure) only show half, including SST_HadISST, AOD_550 and OMI-MLS (@golaz's new run also shows this issue)
![image](https://private-user-images.githubusercontent.com/13056557/256683371-a4b5668d-d305-465e-b9e1-51bb2406631b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg5NDk3MzcsIm5iZiI6MTcxODk0OTQzNywicGF0aCI6Ii8xMzA1NjU1Ny8yNTY2ODMzNzEtYTRiNTY2OGQtZDMwNS00NjVlLWI5ZTEtNTFiYjI0MDY2MzFiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIxVDA1NTcxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQyM2E1NmM0ZmIzMzU3MWM2MTMxMDlmNzRiZTU5YzVlYjI0ZjJhZDM5MDVmMjk0OGNhMjFmZWU4OWIxZDkyMDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.yPcrw8cpI4AVCieWrDmVPS66xBDhenaRBDXBzr8FlI0)
I saw the same issue when developing the GPCP v3.2 processing script. Rotating longitude from [-180,180) to [0, 360) resolved the issue. I suspect that a dependency library for visualization no longer auto consolidating longitude with [-180,180) or [0, 360).
The text was updated successfully, but these errors were encountered: