[ome-devel] Setting Pixels

[Chris Allan]

On Mon, 2009-05-11 at 13:32 +0200, Bernhard Holländer wrote:
> Hi Chris!

:) Hiya.

> 
> 
> >> It's intentional. The design decision was for users to declare the
> >> dimensionality before performing any reads or writes. In fact, what
> >> you're doing is corrupting the pixel buffer that's on disk. There's no
> >> provision to rearrange all the planes when you change the
> >> dimensionality.
> 
> Another quick question:
> 
> Is it important that successive calls to RawPixelStore.setPlane follow
> the plane order specified with PixelsI.setDimensionOrder? I.e. if I
> have dimension order = 'XYZTC' do I have to call make calls to
> setPlane where c varies fastest and z slowest?

No. As far as OMERO is concerned DimensionOrder has no bearing on the
storage or order of access. So, you're free to order the loops however
you wish; start with Z, C or T.

> 
> for z in zs:
>   for t in ts:
>     for c in cs:
>         store.setPlane(buffer, z, c, t)
> 
> Thanks again! Bernhard

Ciao.

-Chris