-
Notifications
You must be signed in to change notification settings - Fork 133
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
Cutensor #1943
base: main
Are you sure you want to change the base?
Cutensor #1943
Conversation
@@ -1,5 +1,4 @@ | |||
# Copyright 2019-2023 ETH Zurich and the DaCe authors. All rights reserved. | |||
from dace.library import register_library | |||
from .nodes import * |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should not remove this statement from a library init, we use it for querying nodes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see I will reintroduce it. I had a circular import issue with them and looked unnecessary in the first glance.
I will reintroduce them and handle the circular import differently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the corresponding tensordot implementation compatible with CuTENSOR v2?
No, but if you approve the design of tensor transpose, I will update the tensordot too. It is possible that I will do it after SC, and first focus on optimizing index permutations on f2dace/dev branch, |
I have added tensor transpose node for cutensor.
I would like you to review the structure of the changes.
I want to use this change to improve the transpose calls in ECRAD.