-
Notifications
You must be signed in to change notification settings - Fork 99
Reusable permutation and transpose #1338
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
Conversation
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.
LGTM, but I think reference tests for the reusable transformations are missing.
Just a comment, but Csr now has 18 (!) function for permutation. IMO that is too much, at least the |
2f2e939
to
79aba5b
Compare
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.
In general LGTM, I would like to discuss the difference between returning both the reuse info with the transposed/permuted matrix and just the reuse info.
If the use case for the reuse info is to be used only once or twice, the current approach makes sense.
If, however, it should be applied in a loop (or similar) then I think returning only the reuse info should lead to more uniform control flow.
6ed38e4
to
e7bfbe3
Compare
cccf80d
to
c7989b1
Compare
c7989b1
to
85e0e76
Compare
85e0e76
to
e21e7ab
Compare
Error: PR already merged! |
As a tool for implementing reusable factories, this adds reusable functionality for all Csr permutation and transpose functions.
It also takes a first step towards making
Permutation
the default representation of a reordering.Closes #1157