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. thanks, alex
Hey Alex, Your project looks very cool. I think it would be a great addition to the community. A module like this would work very well as a scikit. It is very easy to become part of the community. I'm not an expert on this, but I believe you just need to upload your package to PyPI with a scikits.<name> and it will become part of the index. Then, it's about making a web-site, providing good documentation and examples, and getting the word out. Gael V. wrote a nice example about how to get started, but I don't have the link handy. Perhaps he will post it again. Thanks for sharing your code and expertise. Best regards, -Travis On Jan 15, 2012, at 11:32 AM, alex arsenovic 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.
thanks,
alex
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On Mon, Jan 16, 2012 at 12:16:17AM -0600, Travis Oliphant wrote:
I'm not an expert on this, but I believe you just need to upload your package to PyPI with a scikits.<name> and it will become part of the index.
Actually, the 'name' of the package just needs to start with 'scikit', the import name doesn't even have too anymore. Scikits.image and scikit-learn now have import names 'skimage' and 'sklearn'.
Gael V. wrote a nice example about how to get started, but I don't have the link handy. Perhaps he will post it again.
You might be refeering to https://gist.github.com/1433151 Gael
i have been browsing the scikit-image and git docs, trying to feel out the community and workflow. i have a couple quesitons: scikits: i was originally reading these directions. http://projects.scipy.org/scikits/wiki/ScikitsForDevelopers then i looked over the directions linked in previous email from gael, and i am a bit confused. it doesnt appear that the scikit-image and scikit-learn share a common svn repo or use the 'namespace_packages` in its disutils setup. so i am unclear as to the meaning of a scikit, in practice. git: currently my project is hosted at google code, using svn. i see that git is the accepted version control system for scipy, scikit-image, and many others. being that i am sole developer, i dont see much advantage of using git for now, but it appears that it is being adopted, so moving to git is the correct decision. is moving to github from google code recommended or advantageous for scikits? naming: @gael, let me rephrase my understanding of your advice. i can create a git repository that has a name scikit-mwavepy, and the actual python module directory can have an arbitrary name, such as simply mwavepy. is this correct? this brings up the question of naming. are there suggestions as to changing the name mwavepy to something meaningful but also follows some convention for scikits? as a standalone package the name `mwavepy` made sense but as a scikit, it seems as somthing more to the point is appropriate such as skrf, or similar. sphinx/numpydoc: i have some technical questions about documentation concerning sphinx using the numpydoc extensions, is this a correct venue for these or should i post to sphinx mailing lists? thanks alex On 01/16/2012 01:31 AM, Gael Varoquaux wrote:
I'm not an expert on this, but I believe you just need to upload your package to PyPI with a scikits.<name> and it will become part of the index. Actually, the 'name' of the package just needs to start with 'scikit',
On Mon, Jan 16, 2012 at 12:16:17AM -0600, Travis Oliphant wrote: the import name doesn't even have too anymore. Scikits.image and scikit-learn now have import names 'skimage' and 'sklearn'.
Gael V. wrote a nice example about how to get started, but I don't have the link handy. Perhaps he will post it again. You might be refeering to https://gist.github.com/1433151
Gael
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On Wed, Jan 18, 2012 at 09:21:44AM -0500, alex arsenovic wrote:
i was originally reading these directions. http://projects.scipy.org/scikits/wiki/ScikitsForDevelopers then i looked over the directions linked in previous email from gael, and i am a bit confused. it doesnt appear that the scikit-image and scikit-learn share a common svn repo or use the 'namespace_packages` in its disutils setup. so i am unclear as to the meaning of a scikit, in practice.
These are old instructions not up to date. The problem is that most people (including me) do not have write privileges on this page.
is moving to github from google code recommended or advantageous for scikits?
In terms of community pick up probably: there is somewhat of a concensus here, so adopting it will help people pitching in.
@gael, let me rephrase my understanding of your advice. i can create a git repository that has a name scikit-mwavepy, and the actual python module directory can have an arbitrary name, such as simply mwavepy. is this correct?
Yes, but you need to give the name of project (different than the import path) a name starting with 'scikit' if you want it to show up on the scikits web application http://scikits.appspot.com/scikits . This is controlled by the keyword 'name' in the setup.py (e.g. https://github.com/scikit-learn/scikit-learn/blob/master/setup.py#L79) and defines under which name your package will show up on PyPI.
this brings up the question of naming. are there suggestions as to sphinx/numpydoc: i have some technical questions about documentation concerning sphinx using the numpydoc extensions, is this a correct venue for these or should i post to sphinx mailing lists?
Numpy mailing list. Gael
On Wed, Jan 18, 2012 at 2:35 PM, Gael Varoquaux <gael.varoquaux@normalesup.org> wrote:
is moving to github from google code recommended or advantageous for scikits?
In terms of community pick up probably: there is somewhat of a concensus here, so adopting it will help people pitching in.
+1 to Gael's point. Don't underestimate, even if right now you're the sole developer, how much github's fluid workflow can help a project gain new contributors. We have seen, again and again, how having a low barrier of entry for new contributions makes helps a project build a development team. Cheers, f
On 1/18/12 4:51 PM, Fernando Perez wrote:
On Wed, Jan 18, 2012 at 2:35 PM, Gael Varoquaux <gael.varoquaux@normalesup.org> wrote:
is moving to github from google code recommended or advantageous for scikits?
In terms of community pick up probably: there is somewhat of a concensus here, so adopting it will help people pitching in.
+1 to Gael's point. Don't underestimate, even if right now you're the sole developer, how much github's fluid workflow can help a project gain new contributors. We have seen, again and again, how having a low barrier of entry for new contributions makes helps a project build a development team.
In the short term, you can even use SVN to interact with the github repository. https://github.com/blog/966-improved-subversion-client-support http://help.github.com/import-from-subversion/ Thanks, Jason
On Mon, Jan 16, 2012 at 1:32 AM, alex arsenovic <aia8v@virginia.edu> 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:) Cheers, Ralf
all, 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 git page https://github.com/scikit-rf/scikit-rf home page https://github.com/scikit-rf/scikit-rf/wiki docs http://packages.python.org/scikit-rf/# @Ralf, 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. http://packages.python.org/scikit-rf/examples/matching_single_stub.html 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. thanks alex On 01/21/2012 07:11 AM, Ralf Gommers wrote:
On Mon, Jan 16, 2012 at 1:32 AM, alex arsenovic <aia8v@virginia.edu <mailto:aia8v@virginia.edu>> 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:) Cheers, Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On Mon, Jan 23, 2012 at 1:16 AM, alex arsenovic <aia8v@virginia.edu> wrote:
all, 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
git page https://github.com/scikit-rf/scikit-rf home page https://github.com/scikit-rf/scikit-rf/wiki docs http://packages.python.org/scikit-rf/#
Looks good, I'll try it out when I get the chance.
@Ralf, 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.
The first entry (Smith-Chart Diagram) under "Particular Interests".
http://packages.python.org/scikit-rf/examples/matching_single_stub.html 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.
Automated matching, with options to make a trade-off between bandwidth and number of components for example, would be quite useful I think. Graphical aids are more complicated probably, but at least having functions to compute stability, VSWR, etc. for a given network and then plot the contours in a Smith chart wouldn't be hard I think.
Cheers, Ralf
thanks
alex
On 01/21/2012 07:11 AM, Ralf Gommers wrote:
On Mon, Jan 16, 2012 at 1:32 AM, alex arsenovic <aia8v@virginia.edu>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:)
Cheers, Ralf
_______________________________________________ SciPy-Dev mailing listSciPy-Dev@scipy.orghttp://mail.scipy.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
participants (6)
-
alex arsenovic -
Fernando Perez -
Gael Varoquaux -
Jason Grout -
Ralf Gommers -
Travis Oliphant