Conversation
Codecov Report❌ Patch coverage is
... and 32 files with indirect coverage changes 🚀 New features to boost your workflow:
|
|
Your PR no longer requires formatting changes. Thank you for your contribution! |
046f4d0 to
44d6fe6
Compare
11674d6 to
d4e1a03
Compare
|
Had to rebase on top of |
|
(just converted to draft to avoid rerunning all the tests for the various rebases) |
Oh good call, thank you! |
|
FWIW all this is why I normally don't cherry-pick off other branches 😇 |
Fix sources Don't use a storagetype as input for MPS's Remove duplicates in extension more comments Apply suggestions from code review Co-authored-by: Lukas Devos <ldevos98@gmail.com> Fix sources Remove some extra storagetypes
|
OK, I think everything here got addressed, should I put this on R4R and run the full tests? |
lkdvos
left a comment
There was a problem hiding this comment.
I think overall this looks good to go, except for the fact that I don't think it makes sense to include all examples for a GPU version as well.
I do agree that there must be examples about GPU support, but I don't think it makes much sense to translate all of them, since we then also have to maintain all of them 🙃
What I would like instead is for the tests to include some more GPU cases, but I guess that is a way bigger endeavor so I also am happy to just include the changes without that for now
|
I 100% agree about the examples, IMO let me cleanup the multiline stuff a little and try to write a few tests that will actually cover the changes. |
f8b5f86 to
35f3276
Compare
|
Some of the missing coverage here will be fixed once the Algorithm and Driver changes hit at MatrixAlgebraKit, I'll try to add a few more tests for the MPOs though |
|
Some of this needs a fix in TensorOperations, which I'm working on, but I think this can be merged and I'll come back and re-enable the tests affected by |
Mostly allowing passing an array type instead of just an element type to allow GPU arrays to back MPS tensors