Images triggering very slow viewing in insight

[jacques2020]

Hi Josh,

thank you for these answers. As you will see on the fork of your gist, I made some progress. I would like to check import using hash code (md5 e.g.) before labeling image for deletion. But doing so, I face once again with the initial issue of this ticket, the slow access to the image. I agree that it is a bug, but to my mind due to the way an old version of omero imported the image. A good attempt to reproduce would be to import the image in an old version then upgrade. We still use images generated in the same way (though with an updated version of Andor solis software) and found no issue.

By the way, in getting hash code, I was wondering whether omero offer a way to hash the downloaded original file or at least a possibility to read the image file using the embedded bioformat. Or would you recommend an other strategy to ensure that the newly imported image is an integral and non corrupted copy of the old original file. Maybe omero already to such a test at importing ?
Thank you for your help

Best

Jacques

[jmoore]

thank you for these answers.

Gladly.

But doing so, I face once again with the initial issue of this ticket, the slow access to the image.

You're looking to get a checksum for the original archived files? If so, have you tried loading the sha1's via HQL?

I agree that it is a bug, but to my mind due to the way an old version of omero imported the image. A good attempt to reproduce would be to import the image in an old version then upgrade.

Agreed.

By the way, in getting hash code, I was wondering whether omero offer a way to hash the downloaded original file or at least a possibility to read the image file using the embedded bioformat. Or would you recommend an other strategy to ensure that the newly imported image is an integral and non corrupted copy of the old original file. Maybe omero already to such a test at importing ?

Definitely. See https://www.openmicroscopy.org/site/support/omero5.2/developers/ImportFS.html?highlight=checksum and https://www.openmicroscopy.org/site/support/omero5.2/users/cli/import.html?highlight=checksum_algorithm. The --checksum_algorithm can be used (in OMERO5+) to choose which algorithm is chosen. In OMERO4, only sha1 was available and is still the default. (The server-side configuration "omero.checksum.supported" determines what's available and used by default)
Cheers,
~Josh.