On 23/04/2010 10:30 AM, williamol...@comcast.net wrote:
I use pylab.plot(x,y) for exploring or debugging some functions or
subroutines.
I would like to cycle through 2 or more plot windows, in a simple way
that won't force me to entangle the code in bothersome ways. But I
can't seem to get mor
Hello,
I'm trying to plot 0.5x0.5 global data. I'm currently using
pcolormesh. I have a log color scale and haven't been able to use
contourf succesfully for some reason. If I use imshow, it seems to be
too 'bleedy'.
Is there a method for plotting that does some more 'smoothing'
interpolation of
On Apr 22, 2010, at 12:28 PM, Gökhan Sever
wrote:
> Hello,
>
> Consider my simple test case:
>
> import matplotlib.pyplot as plt
>
> fp = plt.figure()
> ax1 = fp.add_subplot(4,1,1)
> ax1.plot(range(10))
> ax2 = fp.add_subplot(4,1,2)
> ax2.plot(range(10))
> ax1.xaxis.set_major_locator (plt.N
I use pylab.plot(x,y) for exploring or debugging some functions or subroutines.
I would like to cycle through 2 or more plot windows, in a simple way that
won't force me to entangle the code in bothersome ways. But I can't seem to get
more than one plot window to open per launch.
Here is an ex
On Thu, Apr 22, 2010 at 4:44 PM, Carlos Grohmann
wrote:
> Hi all,
>
> I'm getting this weird behavior of legend. I always get two symbols in
> front of the labels, instead of one.
> Did anyone experienced this before?
>
> I'm working with MPL in a WxPython app.
>
> code snippet:
>
>
> [code]
>
Hi all,
I'm getting this weird behavior of legend. I always get two symbols in
front of the labels, instead of one.
Did anyone experienced this before?
I'm working with MPL in a WxPython app.
code snippet:
[code]
for i in range(len(self.idxPlan)):
x = self.PeigenLis
Hello,
Consider my simple test case:
import matplotlib.pyplot as plt
fp = plt.figure()
ax1 = fp.add_subplot(4,1,1)
ax1.plot(range(10))
ax2 = fp.add_subplot(4,1,2)
ax2.plot(range(10))
ax1.xaxis.set_major_locator (plt.NullLocator ())
ax3 = fp.add_subplot(4,1,3)
ax3.plot(range(10))
# Can't turn of
If I rotate an axes3D instance with a zlabel
far enough so that the ticks and label "switch sides",
but so that the xlabel and ylabel remain at the bottom,
then the zlabel does not rotate 180 degrees,
as it should to look right. (If I then tilt it so
that the xlabel and the ylabel move to the top,
On Thu, Apr 22, 2010 at 3:42 AM, Matthias Michler
wrote:
> Hi Gökhan,
>
> Just to make one point clear to me. Do you agree that the following is the
> expected behavior of your suggestion to use
> event.inaxes.grid(which='minormajor') after 'g'?
>
> If only the major tick grid lines are shown and
On Thu, Apr 22, 2010 at 3:25 AM, Matthias Michler
wrote:
> Hi Gökhan,
>
> with the attached test.py I generated the attached files 'pic?.png' and I'm
> sorry, I don't get the problem. For me ax.grid(False, which='majorminor')
> removes major and minor ticks on x- and y-axis.
>
> Maybe I changed so
Actually which backend are you using? I'd like to try this to see what happens
if show() is called more than once.
--Michiel.
--- On Tue, 4/20/10, Antony Lee wrote:
That would be a solution, indeed. However, is there really no way of coming
back to a pre-plt.show() state once all windows are
On Wednesday 21 April 2010 19:06:09 Gökhan Sever wrote:
> On Wed, Apr 21, 2010 at 4:39 AM, Matthias Michler
>
> wrote:
> > I think it works like expected, i.e. it toggles the state of showing grid
> > lines for minor and major ticks.
> > The problem it the case were people set only major tick grid
12 matches
Mail list logo
