Re: [Matplotlib-users] GridSpec Index Order

2010-10-26 Thread Jae-Joon Lee
Try this. def get_indx(irow, icol): return irow*4+icol ax = plt.subplot(gs[get_indx(0,3):get_indx(3,3)]) With 1d slicing, the axes will occupy the rectangle defined by the start and stop location. For example, gs[i:j] will occupy the rectangular area between gs[i] and gs[j-1]. Let me kno

Re: [Matplotlib-users] GridSpec Index Order

2010-10-25 Thread Nikolaus Rath
On 10/25/2010 11:18 AM, Jae-Joon Lee wrote: > On Mon, Oct 25, 2010 at 10:45 PM, Nikolaus Rath wrote: >> So I have to instantiate GridSpec with a (rows, column), but when I >> index the grid I have to use (column, row). >> >> Is there any reason for this counterintuitive behaviour? >> > > This is

Re: [Matplotlib-users] GridSpec Index Order

2010-10-25 Thread Jae-Joon Lee
On Mon, Oct 25, 2010 at 10:45 PM, Nikolaus Rath wrote: > So I have to instantiate GridSpec with a (rows, column), but when I > index the grid I have to use (column, row). > > Is there any reason for this counterintuitive behaviour? > This is not an intended behavior but a bug which affects a grid

[Matplotlib-users] GridSpec Index Order

2010-10-25 Thread Nikolaus Rath
Hello, I just noticed that in order to get a 3 row by 4 column grid, I have to do import matplotlib.pyplot as plt from matplotlib.gridspec import GridSpec def make_ticklabels_invisible(fig): for i, ax in enumerate(fig.axes): ax.text(0.5, 0.5, "ax%d" % (i+1), v