Skip to content

Inconsistent parsing of longitudes across cpu architectures #3395

Closed Answered by dcamron
stackjohn asked this question in Q&A
Discussion options

You must be logged in to vote

parse_cf primarily reads standard grid_mapping (or similar) metadata and creates a helper coordinate for cartopy and pyproj access to this projection information. It does not modify your existing coordinates. If you check out ds1.longitude you should see these same differences without MetPy being involved at all.

Given the warning in your x86 output

python3.11/site-packages/gribapi/__init__.py:23: UserWarning: ecCodes 2.31.0 or higher is recommended. You are running version 2.16.0

that is not visible in your osx-arm64 output, my gut spies different versions in your underlying ecCodes library, which is an important dependency for reading grib via the python eccodes library and cfgrib. I d…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@stackjohn
Comment options

Answer selected by stackjohn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
Type: Bug Something is not working like it should
2 participants
Converted from issue

This discussion was converted from issue #3392 on February 12, 2024 19:39.