Exponential#465
Open
sanderdemeyer wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This changes the current way of calculating the exponential (using
LinearAlgebra) to the one recently implemented inMatrixAlgebraKit(see QuantumKitHub/MatrixAlgebraKit.jl#94). This will not yet work, since there is no new version of MatrixAlgebraKit tagged yet. I just wanted to start the discussion here already.I added both
exp!(t)andexp!(tau, t). I added the special case where t is real and tau is complex, whenexp!cannot overwrite the original tensor and instead a new one is allocated. Suggestions on how to best do this are definitely appreciated.I still need to add some tests. We can definitely add some tests on whether the output tensor has the expected
scalartype, and whetherexp!(copy(a)) == exp!((1.0, copy(a)), but suggestions on more nontrivial tests are also welcome.