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

Add auto_optimize to the options #24

Closed
philip-paul-mueller opened this issue Oct 2, 2024 · 1 comment
Closed

Add auto_optimize to the options #24

philip-paul-mueller opened this issue Oct 2, 2024 · 1 comment

Comments

@philip-paul-mueller
Copy link
Contributor

Even if it is just the DaCe version this option would allow us to do some simple benchmarks.

philip-paul-mueller added a commit to philip-paul-mueller/jace that referenced this issue Oct 2, 2024
The auto optimizer is disabled and must be enabled explicitly.
This will be the behaviour will be maintained at least until the map fusion PR is merged.

Essentially this commit addresses issues:
- [issue#24](GridTools#24)
- [issue#25](GridTools#25)
@philip-paul-mueller
Copy link
Contributor Author

Solved by PR#26.

philip-paul-mueller added a commit that referenced this issue Oct 4, 2024
This commit addresses the following issues:
- It adds an implementation for auto optimizer
(#24).
The current implementation is not likely to stay, since it essentially
uses DaCe's version, which is known to have problems with JaCe's SDFGs.
- It allows to run stuff on GPU
(#25).
While it is possible it is still needed that the user explicitly specify
it, JAX does an auto detection.
- Instead of returning NumPy arrays JaCe now returns `jax.Array` objects
(#22).
This goes in tandem with a reworking of the type annotation, which was
wrong before (and can not be correctly made).
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

No branches or pull requests

1 participant