[SciPy-Dev] mwavepy scikit
Sun Jan 22 11:16:24 CST 2012
thanks for the feedback. i have begun the move of mwavepy into a
scikit called `scikit-rf`, with an import path of `skrf`, and short-hand
import convention of `rf`. this seems to roughly follow the conventions
of scikit-learn and scikit-image, and i think the names work well.
i am learning git it the process, and am starting to see why everyone
enjoys it so much.
here are the relevant links
i am unsure which program you are referring to (hard to tell from
that page), but i think i understand generally what you want, perhaps a
look at this page may be helpful.
if you want a graphical-aided solution this can probably be done with
skrf as well, if you are still interested, you can send me an email with
more details and ill take hack at it.
to respond to your request within a larger perspective, i have been
thinking about making some specific application programs out of skrf,
such as automated matching functions and the like. although skrf itself
is meant to provide simple building blocks, adding usable application
examples may be useful.
On 01/21/2012 07:11 AM, Ralf Gommers wrote:
> On Mon, Jan 16, 2012 at 1:32 AM, alex arsenovic <firstname.lastname@example.org
> <mailto:email@example.com>> wrote:
> hello, my name is alex arsenovic. i am the author of the python module
> mwavepy, which is a package for RF/microwave engineering.
> homepage: http://code.google.com/p/mwavepy/
> docs: http://packages.python.org/mwavepy/#
> it is my understanding that scipy doesnt currently have the
> functionality provided by mwavepy, and it seems as though it would
> be a
> valuable module to have, similar to the rf-toolbox in matlab.
> i was entertaining the idea of making a sci-kit for mwavepy, and was
> curious about the scipy-dev community's opinion on this. does a module
> like this belong as a sci-kit? if so, i have numerous questions as to
> what are the next steps.
> Hi Alex, making your project a scikit seems like a good idea. I
> actually tried to use mwavepy about two years ago for some basic
> matching network design. Back then I ran into a number of issues and
> in the end gave up, but it looks like your project came a long way
> since then. Whether or not you make it a scikit, definitely move to
> github though! That would have made the difference for me in
> submitting a few patches instead of just hacking around the first
> issues I encountered.
> In the end I went back to using the free Dellsperger program
> (http://fritz.dellsperger.net/) plus LTSpice. The former has a
> nice GUI and some plotting options like stability and VSWR contours
> that are quite handy, so if you're taking feature requests
> consider this one:)
> SciPy-Dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev