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
Deprecate mdft #20246
Comments
Hi @oscargus! That seems reasonable. Could you expand a bit on how each of these would be used and how the output would look? |
Not sure if I fully understand the question, but here is an example:
As seen, the output of |
For use cases, I use them every now and then when I need a DFT matrix (and not computing the DFT of an input sequence through FFT). There is also the related issue of how to scale these matrices and the direction of the phase shift for DFT and FFT, see #15804. But that is a different issue. The current deprecation is simply a way to keep identical code in a single place. |
Yes, that's what I meant. The deprecation warning will point people to come and look at the information here so showing the alternatives and how to change their code is useful. |
It has been pointed out that |
Hi, not sure what the status of this issue is, but I noticed that there is no entry for sympy.matrices.expressions.fourier in the API reference documentation. |
There's a lot of bits and pieces of docstrings that are missing from the API documentation. Someone needs to go through and add them all (ideally by replacing explicit |
There is a fully functioning
DFT
class inmatrices.expressions.fourier
, so themdft
method inphysics.matrices
should be deprecated.If one would like identical behavior (an evaluated matrix), one should replace
mdft(4)
withDFT(4).as_explicit()
.This is the deprecation removal tracking issue.
The text was updated successfully, but these errors were encountered: