matplotlib-devel Mailing List for matplotlib

If you are using python for high performance or scientific computing,
could I ask you to send me a blurb (one or two sentences) on what you
are using it for and if you have any publications or references
related to this work (the refs don't have to be specifically about the
python stuff) please include them (extra points for bibtex).
I am writing some grant text justifying python in scientific computing
and would like to have a range of examples across disciplines to
provide. 
If I could get these today or tomorrow that would be very helpful!
Please send these to me off list.
Thanks!
JDH

John,
Sorry about that - you didn't miss any emails. I put it on my to-do list 
and then it got swamped w/ other work and I sort of forgot about it.
We've made a few bug fixes w/ regard to keyboard focus so I incorporated 
those into the Fernando's version of the backend. Attached is the file 
that contains Fernando's mod's for ipython and those bug fixes. Everything 
seems to be working fine w/ his changes.
Ted
At 09:40 PM 5/17/2005, you wrote:
> >>>>> "Ted" == Ted Drain <ted...@jp...> writes:
>
> Ted> Sounds good. I'll take a look at it tomorrow (Thursday).
>
> Fernando> With these changes and the corresponding ones to ipython
> Fernando> (not in CVS yet, give me a day or two), it becomes
> Fernando> possible to use ipython to interactively drive Qt
> Fernando> applications, including matplotlib interactive plotting
> Fernando> with the QtAgg backend.
>
> >> Hey guys thanks for working on this -- Ted and colleagues at
> >> JPL, if you haven't used ipython for interactive plotting with
> >> mpl, it is very nice, and I definitely recommend giving it a
> >> try when Fernando gets his changes in CVS. Could you all look
> >> over this patch and make sure it doesn't conflict with anything
> >> your group is doing with the qt backend and if it looks good to
> >> you I'll merge it in.
> >>
> >> JDH
>
>Hi Ted,
>
>Any word on this patch? (did I mess an email?)
>
>JDH

On Tue, 2005年05月17日 at 10:55 -0500, John Hunter wrote:
> >>>>> "Patrik" == Patrik Simons <pat...@ne...> writes:
> 
> Patrik> # Should show orange bars, but shows white, grey, and
> Patrik> black bars. from matplotlib.pylab import * figure() t =
> Patrik> [1,2,3] bar(t, t, color=(1.0, 0.5, 0.0)) show()
> Patrik> Is this surprising behavior really what you want?
> 
> This is a corner case. matplotlib is pretty friendly when you set
> colors. In particular, it allows you to use a float and it interprets
> it as grayscale or an rgb tuple. What you are bumping into is the
> unusual case when the length of your data is exactly three, and it is
> ambiguous whether you want three grayscale values, different for each
> bar, or a single rgb value for all three bars. It wouldn't happen
> with 10 bars because a 10 length tuple of grayscale floats is not
> ambiguous.
> 
> You can disambiguate by using hex strings or colorname strings
Yes, and that is what I had to do with the colors I got from a
colormap:
 color = rgb2hex(colormap(x)[:3])
However, what I really would have hoped for is a color class so that I
wouldn't have to worry about rgb versus rgba and the problem above. For
instance, colormap(x) would return a color instance that I can pass to
bar(), and bar() would also understand rgba automatically.
Something like:
import colors
class Color:
 def __init__(self, color):
 self.color = colors.colorConverter.to_rgba(color)
 def __getitem__(self, i):
 return self.color[i]
 def to_hex(self):
 return colors.rgb2hex(self.color[:3])
 def to_rgb(self):
 return self.color[:3]
 def to_rgba(self):
 return self.color
 etc.
-- 
Patrik