On Oct 9, 2010, at 10:46 PM, Matthew Brett wrote:
Hi,
On Sat, Oct 9, 2010 at 7:30 PM, Eric Firing efir...@hawaii.edu wrote:
https://sourceforge.net/tracker/?func=detailaid=2973874group_id=80706atid=560720
Would someone with a Mac please look at this bug and say whether it is
occurring
On Sep 29, 2010, at 1:06 PM, Jeremy Lounds wrote:
Hello again,
I am not sure if this is a matplotlib question, or a basemap one. The
sample code I found on Google for this either broke my script or
didn't change the end result.
I am attempting to turn the border (frame?) off altogether.
On Sep 29, 2010, at 2:00 PM, Jeremy Lounds wrote:
On Wed, Sep 29, 2010 at 1:21 PM, Tony S Yu tsy...@gmail.com wrote:
On Sep 29, 2010, at 1:06 PM, Jeremy Lounds wrote:
I am attempting to turn the border (frame?) off altogether. Here is
the script, with some sections kept out for brevity
On Sep 3, 2010, at 10:23 AM, Sébastien Barthélemy wrote:
CC to matplotlib-devel matplotlib-users
2010/9/3 Tony S Yu tsy...@gmail.com:
On Sep 3, 2010, at 4:33 AM, Sébastien Barthélemy wrote:
Hello,
While using sage [1], I got problems drawing a line: for some reason,
the points
On Jul 30, 2010, at 8:04 PM, Jae-Joon Lee wrote:
I don't think this is just an issue of bbox_inches option. For
example, if you create an axes of rect=[0,0,1,1] and save the figure
(w/o bbox_inches option), you will see a similar behavior.
Also, I believe that the result depends on the
On Jul 30, 2010, at 10:54 AM, Damon McDougall wrote:
Hi,
I'm interested in fiddling around with the matplotlib source. Let's say we
set up various things:
from matplotlib.figure import Figure()
from matplotlib.backends.backend_pdf import FigureCanvasPdf as FigureCanvas
fig =
On Jul 22, 2010, at 8:59 AM, John Hunter wrote:
On Thu, Jul 22, 2010 at 7:40 AM, Michiel de Hoon mjldeh...@yahoo.com wrote:
Is a backend required to implement a get_renderer method? I only see it
implemented in backend_agg.py, and it's missing in backend_bases.py,
backend_template.py,
On Jul 22, 2010, at 10:07 AM, John Hunter wrote:
On Thu, Jul 22, 2010 at 8:57 AM, Tony S Yu tsyu80@
According to backend_bases.FigureCanvas, a renderer attr is not
guaranteed either.
The Agg* backends rely on get_renderer so that they can get a properly
sized renderer on figure resizes
Unused whitespace is a pet-peeve of mine, so I tend to use bbox_inches='tight'
when saving figures. However, when producing publications, I want figures with
a very specific size (i.e., fit column width of page), but calling
bbox_inches='tight' changes the figure size. Stretching to fit is out
On Jul 21, 2010, at 11:26 PM, John Hunter wrote:
On Wed, Jul 21, 2010 at 10:09 PM, Tony S Yu tsy...@gmail.com wrote:
Wow, I don't see that at all. I'm on OS X, mpl svn HEAD (r8567), and Qt4Agg.
I don't have GTK installed, so unfortunately, I can't really do a proper
comparison. Here's
On Jul 16, 2010, at 4:08 PM, Eric Firing wrote:
On 07/16/2010 09:45 AM, Tony S Yu wrote:
I recently noticed that setting the dpi for savefig doesn't work as
expected when saving to pdf. Take the following code, for example:
import matplotlib.pyplot as plt
plt.figure(figsize=(8,6
I recently noticed that setting the dpi for savefig doesn't work as expected
when saving to pdf. Take the following code, for example:
import matplotlib.pyplot as plt
plt.figure(figsize=(8,6))
plt.plot([1,2])
plt.savefig('test.png', dpi=100)
plt.savefig('test.pdf', dpi=100)
The
The recent nasty import behavior thread motivated me to post an issue I've
been having with matplotlib and chaco. (I've posted to the Chaco list
previously, without much luck.)
If I import matplotlib and chaco at the same time, I get a segmentation fault
in the _path.so plugin. Below is a
in __dyld__dyld_start ()
(gdb) bt
#0 0x7fff5fc01028 in __dyld__dyld_start ()
#1 0x0001 in ?? ()
(gdb)
#-
I'm not very experienced with gdb, so I'm not sure if I'm doing something
wrong.
Thanks,
-Tony
On 07/08/2010 12:13 PM, Tony S Yu wrote:
The recent nasty import behavior
traceback on pastebin: http://pastebin.com/ViefksDC
Are there conflicting versions of agg?
-Tony
On 07/08/2010 12:13 PM, Tony S Yu wrote:
The recent nasty import behavior thread motivated me to post an issue I've
been having with matplotlib and chaco. (I've posted to the Chaco list
previously
On Jul 8, 2010, at 2:51 PM, Michael Droettboom wrote:
On 07/08/2010 02:38 PM, John Hunter wrote:
On Thu, Jul 8, 2010 at 1:25 PM, Tony S Yutsy...@gmail.com wrote:
On Jul 8, 2010, at 12:27 PM, Michael Droettboom wrote:
Can you get a gdb backtrace?
Mike
Ignore my last email. The
On Jun 1, 2010, at 8:59 AM, João Luís Silva wrote:
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):
[snip]
File
I'm running the Qt4 backend, and I noticed that I'd frequently get error
messages saying I was pressing unrecognized keys. It turns out that the
direction keys aren't recognized in the qt4 backend. (I'm using direction keys
to switch between spaces in OSX, so this error gets triggered quite
It seems that changes introduced in r8218 drastically changed how `hist`
handles Python lists.
For example, the histogram given by the following snippet, works as expected:
x = np.random.randn(100)
plt.hist(x)
However, if you pass a 1D list to `hist`, the 1D list is cast to a list of
On Apr 24, 2010, at 4:25 AM, Michiel de Hoon wrote:
Hi everybody,
A number of years ago I wrote a function to do Lowess smoothing to calculate
a smooth curve through a scatter plot. I copied an example script below and
attached the resulting figure to this mail.
I think that such a
I get inconsistent behavior when plotting multiple sets of data with plt.hist.
Here's a quick example:
import numpy as np
import matplotlib.pyplot as plt
x = np.random.randn(10)
y = np.random.randn(9)
plt.hist([x, y])
The above code plots two sets of histograms, as expected. My data sets
Hi Claus,
I fixed the non-Textmate issues (i.e. everything before the P.S. in my original
email), but the TextMate issue remains.
I've had a friend confirm this issue (i.e. hanging on plot calls when scripts
are run in Textmate) on his system, and it sounds like you're confirming the
issue as
On Nov 30, 2009, at 4:34 AM, Andrew Straw wrote:
However, with svn r7985, the trunk fails to find the tests. This is so
weird. There's nothing in that commit that I can see that should cause
the failure, but it seems repeatable. r7984 doesn't have it and r7985
does. And it appears to be
On Nov 30, 2009, at 9:09 AM, Jcmottram wrote:
Hi,
I've been having an almost identical problem with described above with
the MacOSX backend. When I switched to the TkAgg backend, the segfault
occurs when I try pylab.close() instead.
I may have had the same problem. Do you happen to
On Sep 28, 2009, at 2:14 AM, John Hunter wrote:
in case anyone has some suggestions, I'm forwarding this from the
sage list
-- Forwarded message --
From: William Stein wst...@gmail.com
Date: Sun, Sep 27, 2009 at 10:51 PM
Subject: OS X 10.6 port
To: sage-devel
Currently, Arc in matplotlib.patches requires that it be called with
kwarg ``fill=False``. Was this behavior intentional? The code suggests
that a default value was left out of the kwarg lookup.
I've attached a simple patch to fix this (it still fails when fill set
to True).
Cheers,
-Tony
When running `pyplot.spy` I ran into the following error:
AttributeError: 'BlendedGenericTransform' object has no attribute
'_interpolation_steps'
Just from pattern matching (I have no idea what's going on in the
code), I noticed that _interpolation_steps was usually called from a
Path
I'm animating a Circle patch with a varying center and radius, and I
noticed that changing the ``radius`` attribute has no effect on the
patch. Currently, ``radius`` is only used to instantiate an Ellipse
object, but updating radius has no effect (i.e. redrawing the patch
doesn't use the
I was using pcolor with very large numbers and a small vrange (vmax - vmin), and ran into a float to integer conversion problem. Large numbers get converted to *negative* integers by astype(see numpy thread)in colors.Colormap.__call__.I'm not sure if this is even worth fixing since almost no one
On Oct 17, 2008, at 7:29 AM, John Hunter wrote:
Hey Tony,
Thanks for the patch, applied to svn r6232. For future patches, could
you send a svn diff from the matplotlib directory containing
setup.py. That way I don't have to think too hard about the patch
level, what kind of patch it is etc
I noticed that one of the animation examples is missing some import
statements. Also, the diff below includes a small change to the
shebang line of another example.
Cheers,
-Tony
anim_imports.diff
Description: Binary data
On Sep 26, 2008, at 5:01 PM, Eric Firing wrote:
Also, if an image cannot be resolved by the output device, info is
lost--one might not see anything at a location where there actually
is a value--whereas with markers, a marker will always show up, and
the only problem is that one can't
Hi Eric,
Sorry for the late reply.
On Sep 27, 2008, at 8:56 PM, Eric Firing wrote:
Actually, I think the most logical thing would be to let the default
None give the old behavior, and require precision=0 to get the new
behavior. What do you think? Is it OK if I make this change? It
When sparse matrices have explicit zero values, `axes.spy` plots those
zero values. This behavior seems unintentional. For example, the
following code should have a main diagonal with markers missing in the
middle, but `spy` currently plots a full main diagonal.
#~~~
import
On Sep 26, 2008, at 2:28 PM, John Hunter wrote:
On Fri, Sep 26, 2008 at 12:39 PM, Tony S Yu [EMAIL PROTECTED] wrote:
+if all(nonzero == False):
+raise ValueError('spy cannot plot sparse zeros
matrix')
Is raising an exception the right choice here -- why
On Sep 26, 2008, at 3:38 PM, John Hunter wrote:
On Fri, Sep 26, 2008 at 2:36 PM, Tony S Yu [EMAIL PROTECTED] wrote:
Actually, now that I think about it: you could plot a trivially
small image
and just adjust the coordinates so that they correspond to the
original
matrix shape
I was reading through custom_projection_example.py and I noticed that
the cla() method was defined twice (with the exact same code) for the
same class. Here's a patch with one of the cla() methods (the one with
fewer comments) deleted.
delete_cla_copy.diff
Description: Binary data
37 matches
Mail list logo
