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

[QST] could you please help me understand how right_inverse work? #1355

Closed
jakedevtec opened this issue Feb 21, 2024 · 6 comments
Closed

[QST] could you please help me understand how right_inverse work? #1355

jakedevtec opened this issue Feb 21, 2024 · 6 comments

Comments

@jakedevtec
Copy link

What is your question?

I am trying to understand how the right_inverse works in the cute.
For example, https://github.com/NVIDIA/cutlass/blob/main/test/python/pycute/test_right_inverse.py#L88
The given input is Layout((2,4,6),(4,1,8)), I just couldn't figure out why the output is (4, 2, 6):(2, 1, 8).

Any help is appreciated!

@jakedevtec
Copy link
Author

@ccecka you might be the right person who can help me?

Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@JieRen98
Copy link

It is about finding an inv_layout of layout, which satisfies layout(inv_layout(i)) = i

@manishucsd
Copy link
Contributor

manishucsd commented Apr 29, 2024

It will be helpful if we can document right_inverse and left_inverse in CuTe docs.
cc: @ccecka, @thakkarV

@irasin
Copy link
Contributor

irasin commented May 19, 2024

+1
we do need some docs about inverse and how they ared used in such as make_tiled_copy

Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants