Skip to content

fix[next]: Fix default value for use_max_domain_range_on_unstructured_shift#2493

Merged
edopao merged 5 commits intoGridTools:mainfrom
tehrengruber:fix_use_max_domain_range_on_unstructured_shift_default_value
Feb 24, 2026
Merged

fix[next]: Fix default value for use_max_domain_range_on_unstructured_shift#2493
edopao merged 5 commits intoGridTools:mainfrom
tehrengruber:fix_use_max_domain_range_on_unstructured_shift_default_value

Conversation

@tehrengruber
Copy link
Copy Markdown
Contributor

#2173 introduced the ability to infer the domain of all as_fieldop statically when given all connectivities at compile time instead of computing everywhere. The previous behavior to compute everywhere was meant to be configurable by specifying use_max_domain_range_on_unstructured_shift=True in the backend. This option however was falsely ignored when all set_at statements had static domains. This PR fixes that and exposes use_max_domain_range_on_unstructured_shift in the dace backend factory.

Comment thread src/gt4py/next/iterator/transforms/pass_manager.py Outdated
Comment thread src/gt4py/next/iterator/transforms/pass_manager.py Outdated
Comment thread src/gt4py/next/iterator/transforms/pass_manager.py Outdated
Comment thread src/gt4py/next/iterator/transforms/pass_manager.py
@edopao edopao merged commit ed0deb4 into GridTools:main Feb 24, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants