allow dtype specification in abs2, rms #1665
Merged
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.
Reference Issue
fixes #1656
What does this implement/fix? Explain your changes.
This PR allows a user to specify a target dtype in abs2 and rms calculations.
This resolves the issue with rms calculation on integer inputs noted in #1656 . For example, if dtype is not specified, we get overflow:
If dtype is specified, we get proper outputs:
Float32 is the default for rms now, as the result will be averaged and then sqrt'ed anyway.
Any other comments?
I've also snuck in a replacement of
np.abs(S)**2
byutil.abs2(S)
in the rms calculation. Not sure how we missed that one before, but it's fixed now.