-
Notifications
You must be signed in to change notification settings - Fork 736
Add warning about complex tensor to spectrogram #1431
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -84,6 +84,14 @@ def spectrogram( | |||||
| ``n_fft // 2 + 1`` and ``n_fft`` is the number of | ||||||
| Fourier bins, and time is the number of window hops (n_frame). | ||||||
| """ | ||||||
| if power is None and not return_complex: | ||||||
| warnings.warn( | ||||||
| "spectrogram now supports returning native complex tensor " | ||||||
mthrok marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| "when `power=None` by setting `return_complex=True`. " | ||||||
| "Currently, the function returns pseudo complex type (..., 2) by default, " | ||||||
|
||||||
| "Currently, the function returns pseudo complex type (..., 2) by default, " | |
| "Currently, this function returns pseudo complex type (..., 2) by default, " |
Outdated
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.
Suggested change
| "Please refer to https://github.com/pytorch/audio/issues/1337 for the detail.") | |
| "Please refer to https://github.com/pytorch/audio/issues/1337 for more details about the migration plan.") |
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
I think we should explicitly mention it's a deprecation warning:
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.
actually even better, we could use https://docs.python.org/3/library/exceptions.html#DeprecationWarning
warnings.warn(msg, category=DeprecationWarning)wheremsgequalsThere 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.
@anjali411
I do not have a preference here but, according to this comment by @gchanan, PyTorch uses
UserWarningfor deprecation, so intorchaudiowe usedUserWarning.However, I see mixed usage in pytorch.
https://github.com/pytorch/pytorch/search?q=DeprecationWarning
https://github.com/pytorch/pytorch/blob/c371542efc31b1abfe6f388042aa3ab0cef935f2/torch/hub.py#L512
Uh oh!
There was an error while loading. Please reload this page.
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.
@anjali411 Do we want to deprecate the pseudo complex in the upcoming release?
The planned migrations phases are as following and I was thinking to deprecate the native complex type in phase 2.
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.
I gave some thoughts on this and now I think it makes more sense to give heads up on deprecation prior to defaulting native complex type.
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.
yup agreed! let's make a note of that in the main tracker issue so that we don't forget