Skip to content
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

Separate out BigFloat FFT #304

Closed
dlfivefifty opened this issue Mar 4, 2016 · 4 comments
Closed

Separate out BigFloat FFT #304

dlfivefifty opened this issue Mar 4, 2016 · 4 comments

Comments

@dlfivefifty
Copy link
Member

This would be useful for other packages, e.g., ToeplitzMatrices.jl

@dlfivefifty
Copy link
Member Author

Maybe it should be moved to FastTransforms.jl?@MikaelSlevinsky

@MikaelSlevinsky
Copy link
Member

It seems like the relevant Julia issue is JuliaLang/julia#5155 and closed pull request is JuliaLang/julia#6193. It seems like eventually there will be something like an FFTW.jl (sub)module part of a StdLib (set of) package(s).

I don't know exactly what the issue is. Is it that the BigFloat FFT in ApproxFun is useful in ToeplitzMatrices, but it's non-sensical to make ToeplitzMatrices dependent on ApproxFun just for a BigFloat FFT?

It would be nice to have a pure-Julia FFT supporting BigFloat with FFTW1-like code generation available @stevengj.

@dlfivefifty
Copy link
Member Author

I just rewrote the BigFloat FFT so that ToeplitzMatrices.jl can work without requiring it, by making the plans <: Base.DCT.Plan, so it's not really a dependancy issue anymore.

It's more to make the functionality available to others without requiring ApproxFun. FastTransforms.jl seems like a more reasonable home for it.

@stevengj
Copy link
Contributor

Maybe SlowTransforms.jl for the BigFloat case? 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants