[Numpy-discussion] Re: odd behaviour of meshgrid with 3 arrays

2024-11-21 Thread Slavin, Jonathan via NumPy-Discussion
Hi Robert, Thanks. I discovered that after I posted. It had been noted as a bug at one point I see. I still kinda feel like it's a bug since the standard way to call it results in very unexpected behavior. But in any case I now know how to get the results I was looking for. Regards, Jon On Thu,

[Numpy-discussion] Re: odd behaviour of meshgrid with 3 arrays

2024-11-21 Thread Robert Kern via NumPy-Discussion
On Thu, Nov 21, 2024 at 2:00 PM Slavin, Jonathan via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hi all, > > I was trying to use meshgrid with three arrays and got some odd results. > Here's a simple example: > xt = np.array([1,2,3,4]) > yt = np.array([6,7,8]) > zt = np.array([12,13])

[Numpy-discussion] odd behaviour of meshgrid with 3 arrays

2024-11-21 Thread Slavin, Jonathan via NumPy-Discussion
Hi all, I was trying to use meshgrid with three arrays and got some odd results. Here's a simple example: xt = np.array([1,2,3,4]) yt = np.array([6,7,8]) zt = np.array([12,13]) xxx,yyy,zzz = np.meshgrid(xt,yt,zt) So I would expect that xxx[0,0,:] = array([1,2,3,4]) instead I get xxx[0,0,:] = array