-
Notifications
You must be signed in to change notification settings - Fork 49
Issues: GridTools/gt4py
cartesian: K-offset writes bound check is failing
#1754
opened Nov 27, 2024 by
FlorianDeconinck
Open
5
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
cartesian: Solidify Field usage between debug and numpy backends
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
#1902
opened Mar 5, 2025 by
twicki
cartesian: expose HorizontalRegions to DaCe
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
module: backend
Related to analysis/backend subpackages
module: dace
Integration with DaCe framework
triage: enhancement
New feature or request
#1900
opened Mar 4, 2025 by
romanc
cartesian: refactor oportunities after dace bridge refactor
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
module: dace
Integration with DaCe framework
triage: enhancement
New feature or request
#1898
opened Mar 4, 2025 by
romanc
next: Multirank jitting
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
triage: enhancement
New feature or request
cartesian: re-evaluate Issues concerning the current version with support only for cartesian grids.
module: backend
Related to analysis/backend subpackages
triage: performance
Performance related issues
InlineThreadLocalTransients
in gt4py/dace bridge
gt4py.cartesian
#1896
opened Mar 3, 2025 by
romanc
next: warning/error for executing a scalar fieldoperator over a 0-dimensional domain
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
triage: bug
Something isn't working
#1892
opened Feb 28, 2025 by
havogt
next: Program with empty domain crashes in gtfn_gpu
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
triage: bug
Something isn't working
cartesian: dace backends missing support for casting in variable k offsets
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
module: backend
Related to analysis/backend subpackages
triage: bug
Something isn't working
#1881
opened Feb 20, 2025 by
romanc
refactor: storage, layout, and devices (mostly cartesian)
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
module: storage
Related to storage subpackage
priority: low
Low priority task
#1880
opened Feb 20, 2025 by
romanc
1 of 5 tasks
next: np.bool_ argument handling broken in Issues concerning the new version with support for non-cartesian grids.
gtfn
backend
gt4py.next
#1861
opened Feb 13, 2025 by
nfarabullini
next: Issues concerning the new version with support for non-cartesian grids.
gt_substitute_compiletime_symbols()
calls ConstantPropagation
gt4py.next
#1837
opened Jan 30, 2025 by
philip-paul-mueller
[build] Pending enhancements to development infrastructure
infrastructure
Issues concerning the development environment and build dependencies
#1829
opened Jan 28, 2025 by
egparedes
15 tasks
[cartesian] out of bound reads in horizontal region not reported
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
#1817
opened Jan 22, 2025 by
romanc
[cartesian] out of bound reads on vertical axis not reported
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
#1816
opened Jan 22, 2025 by
romanc
next: Let of lists breaks UnrollReduce pass
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
#1795
opened Jan 10, 2025 by
tehrengruber
next: improving wrapping in decorators for program/operators
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
priority: low
Low priority task
triage: enhancement
New feature or request
#1769
opened Dec 4, 2024 by
havogt
next: gt4py stencil cache concurrency error during pytest -n
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
#1765
opened Dec 2, 2024 by
muellch
cartesian: K-offset writes bound check is failing
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
#1754
opened Nov 27, 2024 by
FlorianDeconinck
2 tasks
next: GTFN Caching bug
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
#1739
opened Nov 14, 2024 by
tehrengruber
cartesian: Mitigation for K offset write
gt4py.cartesian
Issues concerning the current version with support only for cartesian grids.
#1684
opened Oct 9, 2024 by
FlorianDeconinck
1 task
next: how to do domain inference for dynamic shift
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
#1676
opened Sep 30, 2024 by
havogt
Programs only using cartesian offsets are allowed to be explicitly set as Issues concerning the new version with support for non-cartesian grids.
triage: bug
Something isn't working
unstructured
by the user
gt4py.next
#1645
opened Sep 16, 2024 by
egparedes
Unused contents of the Issues concerning the new version with support for non-cartesian grids.
triage: bug
Something isn't working
offset_provider
dict generate errors with gtfn
backend
gt4py.next
#1644
opened Sep 16, 2024 by
egparedes
next: missing check for capturing fields in programs/field_operators
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
module: frontend
Frontend subpackage
triage: bug
Something isn't working
#1621
opened Aug 28, 2024 by
nfarabullini
next: missing error when calling a program with GPU backend with fields allocated on CPU
gt4py.next
Issues concerning the new version with support for non-cartesian grids.
#1608
opened Aug 8, 2024 by
tehrengruber
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.