Hello, I am interested in contributing to the scikit-signal project, I have been working on a wavelet package recently which I believe would be useful. https://github.com/Cadair/scikit-signal I have been working on this with one of my friends in my office, to analyse one dataset (which is in the git) and it reproduces the same result as his existing IDL code. There are a few other things we are still working on implementing to this, (significance contouring, more flexibility in parameters). On a side note, we also have use for the pyHHT project, to analyse the same data. Also this is my first attempt at contributing to something like this, so sorry if I go wrong! Stuart
Hi Stuart,
I am interested in contributing to the scikit-signal project,
That's great. Have you been following the discussion that's happened about this package earlier on this list? Here's a summary I made - http://brocabrain.blogspot.in/2012/01/scikit-signal-python-for-signal.html
I have been working on a wavelet package recently which I believe would be useful. https://github.com/Cadair/scikit-signal
Wow, I took a look at the wavelet.py code. I, for one would learn like to learn from you. I want to learn to start coding like that.
On a side note, we also have use for the pyHHT project, to analyse the same data.
I don't think pyHHT will be a part of scikit-signal for some time, both are projects in their infancy. Right now I'm working on time-frequency analysis (for the scikit-signal). Although HHT too is ultimately a tool for time-frequency analysis, we need to create enough motivation for using the HHT over other conventional methods. But of course, as an independent project, you are welcome to contribute. I've put a crude version up at https://github.com/jaidevd/pyhht Looking forward to hearing from you. Cheers
Hi Stuart On Tue, Jan 31, 2012 at 5:20 AM, Stuart Mumford <stuart@mumford.me.uk> wrote:
I am interested in contributing to the scikit-signal project, I have been working on a wavelet package recently which I believe would be useful. https://github.com/Cadair/scikit-signal
We'd also be interested in having wavelet code in scikits-image (http://skimage.org), since we need it for denoising (I was planning on just incorporating pywavelets). An advantage is that you'd get a "free" vehicle for distribution and packaging, but since we focus on image processing, there may be reasons why you'd rather have it in a stand-alone package. Regards Stéfan
2012/2/1 Stéfan van der Walt <stefan@sun.ac.za>
Hi Stuart
On Tue, Jan 31, 2012 at 5:20 AM, Stuart Mumford <stuart@mumford.me.uk> wrote:
I am interested in contributing to the scikit-signal project, I have been working on a wavelet package recently which I believe would be useful. https://github.com/Cadair/scikit-signal
We'd also be interested in having wavelet code in scikits-image (http://skimage.org), since we need it for denoising (I was planning on just incorporating pywavelets). An advantage is that you'd get a "free" vehicle for distribution and packaging, but since we focus on image processing, there may be reasons why you'd rather have it in a stand-alone package.
Don't really understand the stand-alone bit, since that is a scikit-signal fork. But I think the above shows that this really belongs in scipy. I think we should either improve scipy.signal.wavelets or look at merging pywavelets into scipy. This particular wheel gets reinvented way too often. Ralf
On Feb 1, 2012, at 12:33 AM, Ralf Gommers wrote:
2012/2/1 Stéfan van der Walt <stefan@sun.ac.za> Hi Stuart
On Tue, Jan 31, 2012 at 5:20 AM, Stuart Mumford <stuart@mumford.me.uk> wrote:
I am interested in contributing to the scikit-signal project, I have been working on a wavelet package recently which I believe would be useful. https://github.com/Cadair/scikit-signal
We'd also be interested in having wavelet code in scikits-image (http://skimage.org), since we need it for denoising (I was planning on just incorporating pywavelets). An advantage is that you'd get a "free" vehicle for distribution and packaging, but since we focus on image processing, there may be reasons why you'd rather have it in a stand-alone package.
Don't really understand the stand-alone bit, since that is a scikit-signal fork. But I think the above shows that this really belongs in scipy. I think we should either improve scipy.signal.wavelets or look at merging pywavelets into scipy. This particular wheel gets reinvented way too often.
+1 --- I've wanted to see a wavelets package in SciPy for a long time. -Travis
Ralf _______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
participants (5)
-
Jaidev Deshpande
-
Ralf Gommers
-
Stuart Mumford
-
Stéfan van der Walt
-
Travis Oliphant