Fix complex cast warning #329
Merged
Conversation
This file contains 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
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.
Summary
This PR modifies the code to eliminate complex -> real casting warnings that have popped up at various places.
Details and comments
To do this I've changed code in a couple places in which a
tensordotoccurs between a real and complex array. The change is essentially convertingnp.tensordot(x, y)tonp.tensordot(x, y.real) + 1j * np.tensordot(x, y.imag)(wherexis typically real andyis the complex array).This eliminated all of the warnings - I'm not 100% sure about efficiency but I'm hoping it shouldn't change anything, as I assume the cost of arithmetic of
np.tensordot(x, y)forycomplex is twice that of whenyis imaginary.