Skip to content
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

Unused contents of the offset_provider dict generate errors with gtfn backend #1644

Open
egparedes opened this issue Sep 16, 2024 · 0 comments
Labels
gt4py.next Issues concerning the new version with support for non-cartesian grids.

Comments

@egparedes
Copy link
Contributor

egparedes commented Sep 16, 2024

Passing unused NeighborTableOffsetProvider items in the offset provider of a cartesian program in gt4py.next (either explicitly set as cartesian or detected automatically) results in errors with the gtfn backend. Moreover, it also seems that passing an offset provider with unused cartesian Dimensions items to unstructured programs also generate an error (although a different one).

This behavior is weird and it would more natural to ignore the content of offset providers which are not used in the program.

This issue was originally found and reported by @nfarabullini and @halungge in the icon4py project (e.g. https://github.com/C2SM/icon4py/blob/db0dbd65ba5d449b483fdf98fd47acdcb1ddf11e/model/common/src/icon4py/model/common/metrics/metric_fields.py#L228)

@egparedes egparedes added the gt4py.next Issues concerning the new version with support for non-cartesian grids. label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gt4py.next Issues concerning the new version with support for non-cartesian grids.
Projects
None yet
Development

No branches or pull requests

1 participant