-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NGFF Plate import - slow and OOM due to many files #40
Comments
Using an alternative approach as suggested by @sbesson and @joshmoore, I tried importing a "metadata only" NGFF plate (where all the binary chunks were missing but all other files were present. e.g.
This allowed me to view images in webclient, set rendering settings and regenerate thumbnails. However, this process is not suitable for production, so it would be useful to emulate these steps as an option in Bio-Formats and OMERO import options. e.g. |
Thanks for the validation, @will-moore! |
As discussed on IDR call today... We are now converting various submissions with custom formats (mostly .pattern files) into NGFF data. This current workaround is to create a 'metadata-only' copy of the Plate (no chunks), in-place import it and then replace the Plate in ManagedRepo with a symlink to the original plate (with chunks). This is kinda painful, so it would be nice to be able to directly import the original Plate, but for OMERO to NOT create an OriginalFile for every chunk (ignore chunks until we actually want to load pixel data). cc @jburel |
This should be fixed by #41 |
Tried downloading from https://cellpainting-gallery.s3.amazonaws.com/cpg0004-lincs/broad/images/2016_04_01_a549_48hr_batch1/images_zarr/SQ00015098__2016-06-08T18_43_42-Measurement1.ome.zarr/ and importing into
idr0125-pilot
server:Summary of import logs:
Start...
Seb: "Looking at the import logs, the issue is that the time to save OriginalFile dramatically increases from a few milliseconds at the beginning of the import"
to ~5s / file currently
Finally...
The text was updated successfully, but these errors were encountered: