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

Identify avoidable use of scipy at runtime #1611

Closed
marcusmueller opened this issue Feb 11, 2018 · 1 comment
Closed

Identify avoidable use of scipy at runtime #1611

marcusmueller opened this issue Feb 11, 2018 · 1 comment

Comments

@marcusmueller
Copy link
Member

#1545 pointed out that there's scipy used at test-time, but there's also a lot of scipy used in run-time tools and examples that we deliver. (gr_plot_*, filter design tool, a lot of the digital, dtv and filter examples, and more).

In many cases, it's a matter of getting fftpack, which is a) part of numpy and b) could probably be replaced with our very own gr::fft code.

We should identify these cases and reduce the usage of optional external dependencies.

@marcusmueller marcusmueller added this to the Release 3.8 milestone Feb 16, 2018
@devnulling devnulling added this to To do in Release 3.9 via automation Jan 21, 2020
@devnulling devnulling modified the milestones: Release 3.8+, Release 3.9 Jan 21, 2020
@nickoe nickoe added the fft label Mar 27, 2020
@mormj mormj moved this from To do to In progress in Release 3.9 Apr 1, 2020
@marcusmueller marcusmueller removed this from the Release 3.9 milestone Nov 7, 2020
@marcusmueller marcusmueller removed this from In progress in Release 3.9 Nov 7, 2020
@marcusmueller
Copy link
Member Author

This seems solved.

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

No branches or pull requests

3 participants