On 07/18/2010 04:58 AM, H Mike Duan wrote:
> Hi,
>
> There seems to be a problem in how 3D surfaces and lines are rendered
> in mplot3d. The following is a simple script that plots a yellow
> sphere, a blue wireframe on the surface of the sphere, and a red
> wireframe outside the sphere. The semi-t
Hi,
Plotting some very small values (~1E-306) will break mpl with the error:
File
"/usr/lib/python2.5/site-packages/matplotlib/backends/backend_agg.py",
line 154, in draw_text
self._renderer.draw_text_image(font.get_image(), int(x), int(y) +
1, angle, gc)
OverflowError: cannot convert
Hi,
Pressing tab, the "Windows" key or the right click key (and maybe
others) on a plot with the GTKAgg or GTK backend causes the following
traceback:
Traceback (most recent call last):
File
"/usr/lib/python2.5/site-packages/matplotlib/backends/backend_gtk.py",
line 264, in key_press_event
On 05/28/2010 09:18 AM, Pearu Peterson wrote:
> , say, every second and the experiment
> can last hours, I have tried two approaches:
> 1) clear axes and plot new experimental data - this is
> slow and takes too much cpu resources.
> 2) remove lines and plot new experimental data - this is
> fast e
Hi,
Using the SVN version the following example fails with:
File "/usr/local/lib/python2.6/dist-packages/matplotlib/colors.py", line
815, in inverse
raise ValueError("Inversion requires valid vmax > vmin")
ValueError: Inversion requires valid vmax > vmin
This was introduced in svn revision
Hi,
annotate and usetex='True' can trigger a traceback if the text is
invalid. A space or an underscore generate this behavior, I haven't
tried others.
Ubuntu 8.10, mpl svn (rev. 7032).
Once again feel free to ignore this, I just feel compelled to report all
mpl bugs :)
JLS
Example:
#-
Paul Kienzle wrote:
> Hi,
>
> What's the status of interactive property editors for mpl graphs?
>
> I would like something that would allow me to change properties such
> as the size and position of the graph, grids, scales, ranges, colors,
> symbols, line styles, fonts, etc., and add annotat
sam tygier wrote:
>
> That is one method that i have used, but i don't think it is ideal. My data
> can be a wide range of things,
> sometimes the coordinates of a bunch of many particles, sometimes the track
> of one. If I save just an array
> of numbers it can get a bit confusing. So it would
Michael Droettboom wrote:
> There seems to have been an indentation error there.
>
> Please update and try again now.
>
All seems to be fine now, thanks.
João Silva
--
This SF.net email is sponsored by:
SourcForge Com
Michael Droettboom wrote:
> Thanks for narrowing this down. I have (hopefully) fixed this in r6864.
>
It did fix my previous examples. However it broke the other form of
markevery, a 2-int tuple. From the set_markevery docs:
Set the markevery property to subsample the plot when using
Michael Droettboom wrote:
> Thanks for the report. I'm not actually able to reproduce this here --
> though I suspect this could be related to the recent path simplification
> changes.
>
> Taking a stab in the dark -- have you tried removing the build directory
> and rebuilding? distutils doe
Hi,
I found a minor bug. Clicking with the pan and zoom tool on a plot with
markers and the markevery option makes the markers disappear.
OS: Ubuntu
Matplotlib svn revision 6861
Backend: GTKAgg. Didn't test any others.
Example script:
import mat
Jan Müller wrote:
> Hi,
>
> The simple code snippet at the end of this mail should plot a single line.
>
I can confirm this bug on Ubuntu running matplotlib svn revision 6827.
However I think it doesn't have to do with the log-scale but with the
big variations on the x-scale and the custom xs
13 matches
Mail list logo
