[ome-users] Question on "omero admin removepyramids"

[Mark Carroll]

On 04/20/2018 01:01 PM, Sascha Neinert wrote:

> to simplify i look at one image only that i have imported twice into the
> same server instance:

Good idea.

> 1) ID as shown in OMERO.web = 823 and import date = 2018-02-21 11:54:19,
> there is one file …/Pixels/823_pyramid of size 32 MB, time stamp is Feb
> 21 12:55
> 2) ID as shown in OMERO.web = 958, there is also one file
> …/Pixels/958_pyramid but of size 16 MB

I can confirm that I see that same pyramid size difference with your
image between the two OMERO versions. I'm further guessing that your two
images are owned by the same user and in the same group.

> In both cases the table pixels has the same value for ‚id‘ and for
> ‚image‘, so i guess that the pyramid files i found are the corresponding
> ones.

That's plausible but don't assume it will be the case for future images. (-:

> I do not really know how to interpret this behaviour - it could be
> harmless and/or working as intended, it just seemed somehow unusual to
> me.

Your original post mentioned using the --endian=little option. In my
experiments the 5.4.0 server gives your image what it detects as being a
big-endian pyramid and in 5.4.5 a little-endian one. If you try your
command with --endian=big then I bet you see 823 come up. If you do
delete that old one then when you try to view the image OMERO will
create a new little-endian pyramid for it.

-- Mark

The University of Dundee is a registered Scottish Charity, No: SC015096