Scipy 1.0 roadmap - wavelets
On 21 September 2013 20:57, Ralf Gommers <ralf.gommers@gmail.com> wrote:
*Wavelets*: add proper wavelets, including discrete wavelet transform. What's there now doesn't make much sense.
There is a package on Wavelets under MIT license, but it looks abandoned for more than a year. Perhaps it could be reintegrated into Scipy, perhaps it would be better to create a scikit-wavelets while we get something of enough quality. http://www.pybytes.com/pywavelets I can step in, if someone helps and guides me. /David.
Daπid <davidmenhur <at> gmail.com> writes: [clip]
http://www.pybytes.com/pywavelets
I can step in, if someone helps and guides me.
I think Ralf is already gone almost the whole way in integrating this. I'm sure he could use some help, though. @Ralf: was your current code somewhere available? -- Pauli Virtanen
On Thu, Sep 26, 2013 at 2:12 PM, Pauli Virtanen <pav@iki.fi> wrote:
Daπid <davidmenhur <at> gmail.com> writes: [clip]
http://www.pybytes.com/pywavelets
I can step in, if someone helps and guides me.
I think Ralf is already gone almost the whole way in integrating this. I'm sure he could use some help, though.
@Ralf: was your current code somewhere available?
Yes, https://github.com/rgommers/pywt. That turned into a slightly larger refactoring (or rewrite) than I had planned. Next step is to finish converting the doctests in doc/source/regression/ to proper unit tests. After that the found issue(s) need to be fixed. I've opened and closed issues for TODOs, https://github.com/rgommers/pywt/issues. The idea is to finish the rewrite without breaking the API, then submit that back to upstream. I'm not sure whether or not that's still being actively developed, but it's the right thing to do. After that it can be cpnverted to a scipy.signal subpackage easily, and only at that point I want to think about cleaning up the API where needed. David, you help is very welcome! Cheers, Ralf
On 26 September 2013 19:24, Ralf Gommers <ralf.gommers@gmail.com> wrote:
David, you help is very welcome!
import pywt Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/PyWavelets-0.2.2-py2.7-linux-x86_64.egg/pywt/__init__.py",
Ok, I am forking the repository. Any suggestion on where to start? Looking at the open issues, I think the most important are creating the tests. What is your status? BTW, installing pywt on Linux I get: line 15, in <module> from ._pywt import * File "_pywt.pyx", line 24, in init pywt._pywt (/home/david/gits/pywt/src/_pywt.c:16572) ImportError: No module named tools.six But it is not in the requirements.
On Fri, Sep 27, 2013 at 10:29 AM, Daπid <davidmenhur@gmail.com> wrote:
On 26 September 2013 19:24, Ralf Gommers <ralf.gommers@gmail.com> wrote:
David, you help is very welcome!
Ok, I am forking the repository. Any suggestion on where to start?
Looking at the open issues, I think the most important are creating the tests. What is your status?
BTW, installing pywt on Linux I get:
import pywt Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/PyWavelets-0.2.2-py2.7-linux-x86_64.egg/pywt/__init__.py", line 15, in <module> from ._pywt import * File "_pywt.pyx", line 24, in init pywt._pywt (/home/david/gits/pywt/src/_pywt.c:16572) ImportError: No module named tools.six
But it is not in the requirements.
It's not an external requirement but shipped in src/pywt/tools/. Due to setuptools weirdness the whole tests/ and tools/ dirs are missing when installing into site-packages. I hadn't noticed because I use in-place builds to develop. Issue at https://github.com/rgommers/pywt/issues/28. Converting the source tree to a more standard layout for Python projects will fix it, I'll go do that. Ralf
participants (3)
-
Daπid -
Pauli Virtanen -
Ralf Gommers