-
Notifications
You must be signed in to change notification settings - Fork 115
Deprecate conv(u, v::AbstractVector, A)
to conv(u, v::Transpose, A)
#577
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 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
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
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
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
Oops, something went wrong.
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.
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.
This could also be
Adjoint
instead ofTranspose
(with no change to the implementation below). Would that make more sense? Would one rather separate a separable kernelH
asH=u*v'
orH=u*transpose(v)
? (Anyone around working with complex-valued 2D-data and separable filters?)Or should that even be
Union{Adjoint{T,<:AbstractVector}, Transpose{T,<:AbstractVector}}
(akaLinearAlgebra.AdjOrTransAbsVec{T}
)?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.
So I thought I'd ping the author of that method in case he has any insight on whether
Transpose
orAdjoint
would be more idiomatic. Somegit blame
s later, I've arrived at JuliaLang/julia@823cff9 where @JeffBezanson added this tosignal.j
almost 13 years ago. So Jeff, what do you say?More seriously, the current code does
transpose
, so the deprecation forconv(u, v, A)
could either beconv(u, transpose(v), A)
orconv(u, conj(v)', A)
, where I find the former more obvious. If we're going with that, it's eitherTranspose
orAdjOrTransAbsVec
, and I tend to prefer the simplerTranspose
for now. We can always wider the signature later if the need arises.Another issue that in light of #403, the argument order
conv(A, u, transpose(v))
might be more future-proof, as there, the first argument plays the role of the input and the second one plays the role of a convolution kernel (as inspired by MATLAB).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.
Letting this sink in a bit more, I think these concerns are non-issues:
transpose
d, that's what the deprecation should do. If we want to similarly allowAdjoint
, we can always do so later.