Thanks! Using pcolor indeed solved the problem. Now my rows and columns are all
nice and even.
Best,
-Michiel.
From: Benjamin Root
To: Michael Droettboom
Cc: Matplotlib Users
Sent: Friday, June 7, 2013 1:40 AM
Subject: Re: [Matplotlib-users] matshow
On Thu, Jun 6, 2013 at 10:14 AM, Michael Droettboom wrote:
> By default (when interpolation="nearest") matplotlib is performing
> nearest neighbor interpolation on the image to the request PDF dpi before
> storing it in the file. This results in rows and columns of unequal size
> because the ra
By default (when interpolation="nearest") matplotlib is performing
nearest neighbor interpolation on the image to the request PDF dpi
before storing it in the file. This results in rows and columns of
unequal size because the ratio from the original image to the
destination resolution is likel
Hi all,
I am trying to draw a heatmap using matshow, which I then save as a PDF.
If I then zoom in in the PDF, I notice that different rows have different
sizes, and different columns have different sizes. It seems that some
rows/columns have twice the height/width as other rows/columns.
Attache
Hi Matthias,
Thanks for the help. The problem is, however, that the 'extent' parameter
only manipulates the range of the (integer) values on the axis. Before
setting the *axis_date property, I need to set the axes data to arrays of
(non-equidistant) floats.
Best Regards,
Micha
Matthias Michler
On Monday 29 March 2010 13:56:51 Atomfried wrote:
> Hi,
>
> is it possible to perform a surface plot a NxM matrix with date-axes?
> Similar to plot_date for 1D-Plots. The dates are available as an N-sized
> (or M-sized) array of float values.
>
> At the moment, I am using imshow or matshow for the
Hi,
is it possible to perform a surface plot a NxM matrix with date-axes?
Similar to plot_date for 1D-Plots. The dates are available as an N-sized (or
M-sized) array of float values.
At the moment, I am using imshow or matshow for the color plots, but the
only way I found to manipulate the axes
On Thu, Sep 17, 2009 at 2:49 AM, Bala subramanian
wrote:
> Friends,
>
> I have a matrix data and i used matshow() function to plot. The plot is
> attached.
>
> 1) After plotting the data, i used xticks() function to change the x-axis
> tick labels from x1 to x12 ( figure attached). Similarly I wan
Friends,
I have a matrix data and i used matshow() function to plot. The plot is
attached.
1) After plotting the data, i used xticks() function to change the x-axis
tick labels from x1 to x12 ( figure attached). Similarly I want to change
the y-axis tick labels into as A,B and C, instead of 0,1,
I am new to matplotlib and I am really impressed.
I have a problem though.
I am not able to get a lower origin in matshow, imshow gives the origin at
bottom when I say origin='lower'
for example
#!/usr/bin/env python
from matplotlib.pylab import *
matshow(rand(64,64),fignum=100,cmap=cm.gray,orig
Thanks again Eric for the updated matshow().
I apologise for repeating:
Since it has been decided (has it?) that matshow will retain the feature
that a new figure is created (with aspect ratio matching the matrix), then
if one adds a colorbar (a typical thing to do), the matrix height is
small
On 3/19/07, Eric Firing <[EMAIL PROTECTED]> wrote:
> One of the matshow anomalies is that it is a pylab function only instead
> of a wrapper for an Axes method, so I made a new Axes.matshow(), and a
> temporary matshow1() pylab function that calls it. Differences between
> matshow() and matshow1(
On Sun, 18 Mar 2007, Eric Firing wrote:
> One of the matshow anomalies is that it is a pylab function only instead
> of a wrapper for an Axes method, so I made a new Axes.matshow(), and a
> temporary matshow1() pylab function that calls it. Differences between
> matshow() and matshow1():
>
> 1) T
Fernando Perez wrote:
[...]
> Frankly, I don't care how it's done: I wrote matshow long ago, back
> when axis('scaled') didn't exist in the first place. If the same
> result can be achieved by other means that are cleaner, I'm sure John
> will accept a patch.
One of the matshow anomalies is that
On 3/16/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
I guess that makes sense.
Personally I'd rather have consistency. I'm not sure why matshow() in
particular needs to have the window shape match the image shape.
Why not just do axis('scaled') within the confines of the window you have?
Tried i
On 3/17/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
A pox on matplotlib's default reply-to-sender!
Resending my reply that went to Fernando alone below.
> On 3/17/07, Fernando Perez <[EMAIL PROTECTED]> wrote:
> > On 3/16/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
> > > Why does pylab.matshow() cre
On 3/16/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
> Why does pylab.matshow() create a new figure by default when no other
> standard pylab function I know of does that? It seems very
> inconsistent for no particular gain, since as always
> figure();matshow(m) will achieve that result if that is w
Why does pylab.matshow() create a new figure by default when no other
standard pylab function I know of does that? It seems very
inconsistent for no particular gain, since as always
figure();matshow(m) will achieve that result if that is what is
desired.
--bb
18 matches
Mail list logo
