I'm in a similar boat with the research on which I'm working, paper and all. I don't know if folks will end up using it or not, but at least it is available (github), if not well advertised to the (decidedly small) niche of folks who would be interested.
Cheers,
Kevin
···
At 10:47pm -0400 Sun, 03 Jun 2012, Tom Dimiduk wrote:
Very few people outside my group use it at the moment, but that looks
to be changing at least a bit. I will hopefully get a paper out about
the code by the end of the summer.
What is your project?
Like probably anyone in this situation, I have written a bunch of little convenience tools working with images, a simple matplotlib based gui to provide richer imshow image interaction (clicking to get pixel coordinates), more user friendly wrappers around scipy functions to do what is at least the most common case for us, and things of that sort.
Is any of this stuff I should be looking to upstream or split off into the start of a scientific imaging library for python?
···
On 06/05/2012 10:14 AM, Kevin Hunter wrote:
At 10:47pm -0400 Sun, 03 Jun 2012, Tom Dimiduk wrote:
Very few people outside my group use it at the moment, but that looks
to be changing at least a bit. I will hopefully get a paper out about
the code by the end of the summer.
I'm in a similar boat with the research on which I'm working, paper and
all. I don't know if folks will end up using it or not, but at least it
is available (github), if not well advertised to the (decidedly small)
niche of folks who would be interested.
Very few people outside my group use it at the moment, but that
looks to be changing at least a bit. I will hopefully get a paper
out about the code by the end of the summer.
I'm in a similar boat with the research on which I'm working, paper
and all. I don't know if folks will end up using it or not, but at
least it is available (github), if not well advertised to the
(decidedly small) niche of folks who would be interested.
What is your project?
Heh. It didn't occur to me that I should answer my own question! 
http://temoaproject.org/
Briefly an energy-economy optimization (EEO) model and surrounding tools. If you just learned what that means, well ... welcome to the (decidedly small) niche!
Like probably anyone in this situation, I have written a bunch of little
convenience tools working with images, a simple matplotlib based gui to
provide richer imshow image interaction (clicking to get pixel
coordinates), more user friendly wrappers around scipy functions to do
what is at least the most common case for us, and things of that sort.
Is any of this stuff I should be looking to upstream or split off into
the start of a scientific imaging library for python?
Potentially. I'm haven't explored that area for my research yet, but I *do* plan for a GUI. (Oh, but if plans were worth a nickel ...) For the types of analysis one generally (well, currently, anyway) does with EEO models, static graphics seem to be the method du jour. Thus, I'm not to the point of manipulating graphics yet, just generating various y(x) graphs with my scripts for later consumption.
Unfortunately, what we (I) do with our various ad-hoc scripts is not at all integrated yet, so we are currently just a (thankful) consumer.
Cheers,
Kevin
···
At 10:25am -0400 Tue, 05 Jun 2012, Tom Dimiduk wrote:
On 06/05/2012 10:14 AM, Kevin Hunter wrote:
At 10:47pm -0400 Sun, 03 Jun 2012, Tom Dimiduk wrote:
Have you had a look at skimage https://github.com/scikits-image ?
BTW I uses matplotlib (and the whole pylab suite) in my projects for all the visualisation.
A (peer reviewed published) example here: https://github.com/Kinetochore-segregation
Best
Guillaume
···
Le 05/06/2012 16:25, Tom Dimiduk a écrit :
Is any of this stuff I should be looking to upstream or split off into
the start of a scientific imaging library for python?
The Spyder (Google Code Archive - Long-term storage for Google Code Project Hosting.) python-based matlab
clone uses matplotlib for plotting.
Python(X,Y) (Google Code Archive - Long-term storage for Google Code Project Hosting.) is an integrated
windows python release that includes a ton of science, engineering,
and mathematics-oriented python packages, including matplotlib.
Numpy uses small bits of matplotlib when building the documentation,
but I don't know if that counts (I think it may even use it for
building matplotlib-related parts of the documentation, in which case
it really doesn't count).
I know someone is working on a pure python backend for the Cantor
advanced mathematics software (Cantor - KDE Applications). The
project only started recently, however (see
LaKademy results – starting development of Python backend to Cantor – Filipe Saraiva's blog ). There is also already a sage
backend for Cantor, which of course uses matplotlib for plotting
because that is what sage uses.
-Todd
···
On Wed, Jun 6, 2012 at 8:01 AM, Guillaume Gay <guillaume@...4007...> wrote:
Le 05/06/2012 16:25, Tom Dimiduk a écrit :
Is any of this stuff I should be looking to upstream or split off into
the start of a scientific imaging library for python?
Have you had a look at skimage https://github.com/scikits-image ?
BTW I uses matplotlib (and the whole pylab suite) in my projects for all
the visualisation.
A (peer reviewed published) example here:
https://github.com/Kinetochore-segregation
Best
Guillaume