Hi Everyone,
Thanks for your suggestions and replies. I initially tried what Anne
suggested, modifying the strides in the third dimension to account for
the 8-byte delimiters between slabs, but I couldn't control the
performance as much as I'd like, and I wasn't entirely sure when and
where "real
On Thu, Apr 22, 2010 at 21:57, David Huard wrote:
> Hi Matt,
> I don't think the memmap code support this. However, you can stack memmaps
> just as easily as arrays, so if you define individual memmaps for each slice
> and stack them (numpy.vstack), the resulting array will behave as a regular
> 3
Hi Matt,
I don't think the memmap code support this. However, you can stack memmaps
just as easily as arrays, so if you define individual memmaps for each slice
and stack them (numpy.vstack), the resulting array will behave as a regular
3D array.
HTH,
David H.
On Wed, Apr 21, 2010 at 3:41 PM,
On 21 April 2010 15:41, Matthew Turk wrote:
> Hi there,
>
> I've quite a bit of unformatted fortran data that I'd like to use as
> input to a memmap, as sort of a staging area for selection of
> subregions to be loaded into RAM. Unfortunately, what I'm running
> into is that the data was output a
On Wed, Apr 21, 2010 at 14:41, Matthew Turk wrote:
> Hi there,
>
> I've quite a bit of unformatted fortran data that I'd like to use as
> input to a memmap, as sort of a staging area for selection of
> subregions to be loaded into RAM. Unfortunately, what I'm running
> into is that the data was o
Hi there,
I've quite a bit of unformatted fortran data that I'd like to use as
input to a memmap, as sort of a staging area for selection of
subregions to be loaded into RAM. Unfortunately, what I'm running
into is that the data was output as a set of "slices" through a 3D
cube, instead of a sing
