[SciPy-Dev] Procedure for new code submission (pyHHT)
Fri Jun 8 14:39:34 CDT 2012
I agree that HHT should remain isolated for the moment. When it
matures, the community can decide where it should reside.
As for the IPR status of the HHT, I want to share the reply Dr Norden
Huang gave when I asked him about it.
"The NASA patent covers only the US. You are free to do whatever outside US
territory as long as you do not make money in the US. Go ahead with your
project, and good luck."
Now, I would assume that this exempts research based on the HHT from
the IPR regulations, even in the US. A lot of people have been doing
it for almost a decade now, and many were Americans. And I don't think
anyone pays or gets paid for using the HHT algorithms for academic
purposes. And anyhow, there are many implementations of HHT on
matlabcentral.com, there are freely available R packages too.
Also, scipy.signal itself has a long way to go before we can include
something like HHT.
On Fri, Jun 8, 2012 at 6:47 PM, Stuart Mumford <firstname.lastname@example.org> wrote:
> I am working on a EMD / HHT code for some analysis I am doing as part of my
> PhD. (It is currently here: https://github.com/Cadair/pyhht (kicked off from
> jaidevd's inital work))
> I was wondering what the general procedure for getting something like this
> included in SciPy is. I know it requires a lot more work to even be
> considered but I would like to focus what I am doing with that end in mind.
> The Web here: http://scipy.github.com/dev-zone.html says that initially you
> should write a SciKit, is this still the way to go or is it fine just to
> create a repo with good quality documentation etc?
> Also is a HHT toolbox something that should be integrated into scipy.signal
> or (at risk of restarting an amusing debate) should it go into
> SciPy-Dev mailing list
More information about the SciPy-Dev