Eric Firing wrote:
> Jordan,
>
> I understand what you wrote. I am a bit worried about the amount of
> complexity it would add to the collection code, however, and it seems
> like it would be useful only in quite special situations--and in those
> situations, there may be reasonable alternative
I have one suggestion, slightly off-topic, and I'm not sure how useful
it would be: you might think about making LineCollection accept a 3-D
numerix array. This came up for me while I was looking at turning the
quiver arrows into line segments. As I understand it (and as the
documentation say
Based on a quick look, I think it would be easy to make LineCollection
and PolyCollection accept a numerix array in place of [(x,y), (x,y),
...] for each line segment or polygon; specifically, this could replaced
by an N x 2 array, where the first column would be x and the second
would be y. B
I'm making an errorbar plot with assymetric errorbars. The docstring says:
xerr and yerr may be any of:
a rank-0, Nx1 Numpy array - symmetric errorbars +/- value
an N-element list or tuple - symmetric errorbars +/- value
a rank-1, Nx2 Numpy array - asymmetric errorbars -c
How about 'plots'? (i.e., a bunch of plot commands)
Perhaps this could also be the function that loops through multiple
lines. For example in matlab you can do
plot (x, y)
plot (x', y')
to plot out a grid -- the columns (or is it the rows..) are looped
through inside the plot command. Is
