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.

Sign up for GitHub

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

Jump to bottom

cartesian: Solidify Field usage between debug and numpy backends #1902

Open
twicki opened this issue Mar 5, 2025 · 0 comments
Open

cartesian: Solidify Field usage between debug and numpy backends #1902

twicki opened this issue Mar 5, 2025 · 0 comments
Labels
gt4py.cartesian Issues concerning the current version with support only for cartesian grids.

Comments

@twicki
Copy link
Contributor

twicki commented Mar 5, 2025

Description

⚠ Work in Progress ⚠

PR #1884 exposed the Field class used in both the numpy and the debug backend in utils/field.py instead of code-generating it directly into the source file. This could be consolidated between the two backends.
@twicki twicki mentioned this issue Mar 5, 2025
Open
1 task
@FlorianDeconinck FlorianDeconinck changed the title Solidify Field usage between debug and numpy backends [cartesian] Solidify Field usage between debug and numpy backends Mar 5, 2025
@FlorianDeconinck FlorianDeconinck added the gt4py.cartesian Issues concerning the current version with support only for cartesian grids. label Mar 5, 2025
@FlorianDeconinck FlorianDeconinck changed the title [cartesian] Solidify Field usage between debug and numpy backends cartesian: Solidify Field usage between debug and numpy backends Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
gt4py.cartesian Issues concerning the current version with support only for cartesian grids.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FlorianDeconinck @twicki