Skip to content
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

Move OMERO pyramid specification to model documentation #55

Merged
merged 6 commits into from Oct 23, 2017

Conversation

melissalinkert
Copy link
Member

Each pyramid contains 5 resolutions for each image plane, with each resolution stored in descending order from largest to smallest XY size.
Each resolution is half the width and height of the previous resolution.

OMERO handles pyramid generation automatically for files that do not already have a stored pyramid, use a supported pixel type,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This last paragraph is unrelated to the Pyramid format. Ideally should be in the OMERO documentation since it's also unrelated to Bio-Formats. Could it be dropped?

Internal OMERO pyramid format v1.0.0
====================================

For files that contain very large images and are not in a format that supports pyramids, OMERO will generate its own
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This first paragraph is largely unrelated to the format description. Could it be replaced with a more appropriate introduction to the pyramid format or moved elsewhere?

Z sections, and/or timepoints.

Each pyramid contains 5 resolutions for each image plane, with each resolution stored in descending order from largest to smallest XY size.
Each resolution is half the width and height of the previous resolution.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be worth mentioning explicitly that these 5 resolutions are separate IFDs.

Also, it made me wonder what the purpose of the JPEG-2000 decompression levels is, if we store and use the separate IFDs and don't actually use the decompression levels in the full-resolution IFD?

@@ -0,0 +1,22 @@
Internal OMERO pyramid format v1.0.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with the rest of the manual, could this be entitled "The OMERO Pyramid format" and move the version to the main text?

@@ -73,6 +73,16 @@ OME-XML
ome-tiff/tools
ome-xml/java-library

**************
OMERO Pyramids
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe make singular "Pyramid" for consistency with the other things in the index.

@melissalinkert
Copy link
Member Author

All comments so far should be addressed with the latest 4 commits.

@rleigh-codelibre
Copy link
Contributor

Thanks, looks good to merge to me.

========================

The OMERO pyramid format is a way of storing very large images for easier visualization.
Currently only v1.0.0 is currently defined.
Copy link
Member

@hflynn hflynn Oct 13, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one little nitpick, you've got currently twice in this sentence, you only need the first one.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be fixed with ee55320

@hflynn
Copy link
Member

hflynn commented Oct 13, 2017

N.B. made https://trello.com/c/LAmAnmOc/591-cross-reference-new-pyramid-doc-in-omero-docs to reference this in the OMERO docs once this is published.

@hflynn
Copy link
Member

hflynn commented Oct 13, 2017

👍

@sbesson sbesson merged commit 9352561 into ome:master Oct 23, 2017
@sbesson sbesson added this to the 5.6.0 milestone Nov 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants