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

fix[next][dace]: Fixed a bug in the map fusion's default parameter #1866

Merged

Conversation

philip-paul-mueller
Copy link
Contributor

MapFusion was behaving as the one from DaCe, i.e. it only did serial fusion by default, now it allows both by default. There are still MapFusionSerial and MapFusionParallel with the respective settings. This commit also changes auto optimizer to explicitly request them.

`MapFusion` was behaving as the one from DaCe, i.e. it only did serial fusion by default, now it allows both by default.
There are still `MapFusionSerial` and `MapFusionParallel` with the respective settings.
This commit also changes auto optimizer to explicitly request them.
@@ -81,11 +83,18 @@ class MapFusion(dace_map_fusion.MapFusion):
def __init__(
self,
strict_dataflow: bool = False,
allow_serial_map_fusion: bool = True,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a matter of taste, but I would make a simpler interface and not expose these 2 new parameters.

For that case teh `can_be_applied()` method never checked if the maps are parallel.
The method to do that was there but not really implemented.
@philip-paul-mueller philip-paul-mueller merged commit 8595cfd into GridTools:main Feb 14, 2025
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.

2 participants