Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

openslide-show-properties(1) [debian man page]

OPENSLIDE-SHOW-PRO(1)						  Users Commands					     OPENSLIDE-SHOW-PRO(1)

NAME
openslide-show-properties - Print OpenSlide properties SYNOPSIS
openslide-show-properties infile DESCRIPTION
Print OpenSlide properties. LIST OF KNOWN PROPERTIES
Properties generated by OpenSlide openslide.vendor The name of the vendor backend. openslide.comment A free-form text comment, the same as returned from openslide_get_comment. openslide.quickhash-1 A non-cryptographic hash of a subset of the slide data. It can be used to uniquely identify a particular virtual slide, but cannot be used to detect file corruption or modification. openslide.background-color The background color of the slide, given as an RGB hex triplet. This property is not always present. Properties from the JPEG backend No properties defined. Properties from the TIFF backend tiff.ImageDescription The contents of the TIFF ImageDescripton tag. tiff.Make The contents of the TIFF Make tag. tiff.Model The contents of the TIFF Model tag. tiff.Software The contents of the TIFF Software tag. tiff.DateTime The contents of the TIFF DateTime tag. tiff.Artist The contents of the TIFF Artist tag. tiff.HostComputer The contents of the TIFF HostComputer tag. tiff.Copyright The contents of the TIFF Copyright tag. tiff.DocumentName The contents of the TIFF DocumentName tag. tiff.XResolution The contents of the TIFF XResolution tag. tiff.YResolution The contents of the TIFF yResolution tag. tiff.XPosition The contents of the TIFF XPosition tag. tiff.YPosition The contents of the TIFF YPosition tag. tiff.ResolutionUnit The contents of the TIFF ResolutionUnit tag. Vendor-specific properties A list of vendor-specific properties can be found on the pages for each vendor format, linked from Supported Virtual Slide Formats[1]. TRESTLE FORMAT
Format single-file pyramidal tiled TIFF, with non-standard metadata and overlaps; additional files can contain more metadata and detailed overlap info File extensions .tif OpenSlide vendor backend trestle OpenSlide ops backend tiff Detection Trestle slides are stored in single-file TIFF format. OpenSlide will detect a file as Trestle if: 1. The file is TIFF. 2. The TIFF Software tag starts with "MedScan". 3. The ImageDescription tag is present. Relevant TIFF tags +-------------------------+---------------------------------------------------+ |Tag | Description | +-------------------------+---------------------------------------------------+ |ImageDescription | Stores some important key-value pairs, see below | +-------------------------+---------------------------------------------------+ |Software | Starts with "MedScan" | +-------------------------+---------------------------------------------------+ |XResolution, YResolution | Seems to store microns-per-pixel (MPP), which may | | | or may not take into account the correct | | | objective power. Note that this is inverted from | | | standard TIFF, which stores pixels-per-unit, not | | | units-per-pixel. | +-------------------------+---------------------------------------------------+ Extra data stored in ImageDescription The ImageDescription tag contains semicolon-delimited key-value pairs. A key-value pair is equals-delimited. We use the OverlapsXY and Background Color keys from the ImageDescription, and ignore the rest. All of these values are stored as properties starting with "trestle.". +-----------------+--------------------------------------------------+ |Key | Description | +-----------------+--------------------------------------------------+ |Background Color | Hex-encoded background color info, assumed to be | | | in the format RRGGBB. | +-----------------+--------------------------------------------------+ |White Balance | Hex-encoded white balance | +-----------------+--------------------------------------------------+ |Objective Power | Reported objective power, often incorrect. | +-----------------+--------------------------------------------------+ |JPEG Quality | The JPEG quality value. | +-----------------+--------------------------------------------------+ |OverlapsXY | Overlaps, see below. | +-----------------+--------------------------------------------------+ TIFF Image Directory Organization The first image in the TIFF file is the full-resolution image. The subsequent images are assumed to be decreasingly sized reduced-resolution images. Overlaps The OverlapsXY pseudo-field encodes a list of tile overlap values as ASCII. Example: "64 64 32 32 16 16" (note the initial space). These values are assumed to represent the amount of overlap between adjacent tiles in pixels, in both X and Y. This example encodes 3 levels worth of overlaps. Further overlaps are assumed to have the value 0. Associated Images None. Known Properties All data encoded in the ImageDescription TIFF field is represented as properties prefixed with "trestle.". Test Data http://openslide.cs.cmu.edu/download/openslide-testdata/Trestle/ HAMAMATSU FORMAT
Format multi-file JPEG/NGR with proprietary metadata and index file formats File extensions .vms, .vmu OpenSlide vendor backend hamamatsu OpenSlide ops backend jpeg for .vms, ngr for .vmu Detection OpenSlide will detect a file as Hamamatsu if: 1. The file given is a INI-style text file. 2. It has a [Virtual Microscope Specimen] (VMS) or [Uncompressed Virtual Microscope Specimen] (VMU) group. 3. The file specifies a positive number of layer (NoLayers>=1). Currently, only one of these focal plane layers is read. 4. If VMS, there are at least 1 row and 1 column of JPEG images (NoJpegColumns and NoJpegRows). 5. The mapfile given by MapFile is a valid readable file in the same directory as the VMS file. 6. The files given by the various ImageFile lines do not exceed the number of rows and columns as specified above. 7. The mapfile and image files are all valid JPEG files or all valid NGR files. 8. The restart interval in each JPEG file is zero, or evenly divides into the number of MCUs per row. 9. The image files (except the map file) all have the same "tile" sizes (see below). Overview The Hamamatsu format consists of an index file (VMS or VMU), 2 or more image files, and (in the case of VMS) an "optimisation" file. Multiple focal planes are ignored, only focal plane 0 is read. Because JPEG does not allow for large files, multiple JPEG files are needed to encode large images. To avoid having many files, the Hamamatsu format uses close to maximum size (65K by 65K) JPEG files. Unfortunately, (unlike TIFF) JPEG provides very poor support for random-access decoding of parts of a file. To get around this, JPEG restart markers are placed at regular intervals, and these offsets are specified in the optimisation file. With restart markers identified, OpenSlide can treat JPEG as a tiled format, where the height is the height of an MCU row, and the width is the number of MCUs per row divided by the restart marker interval times the width of an MCU. (This often leads to oddly-shaped and inefficient tiles of 8x2048, for example.) Unfortunately, the optimisation file does not give the location of every restart marker, only the ones found at the beginning of an MCU row. It also seems that the file ends early, and does not give the location of the restart marker at the last MCU row of the last image file. Thus, the optimisation file can only be taken as a hint, and cannot be trusted. The entire set of JPEG files must be scanned for restart markers in order to facilitate random access. OpenSlide does this lazily as needed, and also in a background thread that runs only when OpenSlide is otherwise idle. The map file is a lower-resolution version of the other images, and can be used to make a 2-level JPEG pyramid. JPEG also allows for lower-resolution decoding, so further pyramid levels are synthesized from each JPEG file. VMS File The .vms file is the main index file for the VMS format. It is a Windows INI-style key-value pair file, with sections. Only keys in the Virtual Microscope Specimen group are read by OpenSlide. Here are known keys from the file: +-----------------------+---------------------------------------------------+ |Key | Description | +-----------------------+---------------------------------------------------+ |NoLayers | Number of layers, currently must be 1 to be | | | accepted | +-----------------------+---------------------------------------------------+ |NoJpegColumns | Number of JPEG files across, given in ImageFile | | | attributes | +-----------------------+---------------------------------------------------+ |NoJpegRows | Number of JPEG files down, given in ImageFile | | | attributes | +-----------------------+---------------------------------------------------+ |ImageFile | Semantically equivalent to ImageFile(0,0,0), | | | though not specified that way. The image in | | | position (0,0,0) of the set of images | +-----------------------+---------------------------------------------------+ |ImageFile(x,y) | Semantically equivalent to ImageFile(0,x,y), | | | though not specified that way. The image in | | | position (0,x,y) of the set of images | +-----------------------+---------------------------------------------------+ |ImageFile(z,x,y) | Where x and y are non-negative integers. Both x | | | and y cannot be 0. z is a positive integer. These | | | are the images that make up the virtual slide, as | | | a concatenation of JPEG images. x and y specify | | | the location of each JPEG, z specifies the focal | | | plane | +-----------------------+---------------------------------------------------+ |MapFile | A lower-resolution version of all the ImageFiles | +-----------------------+---------------------------------------------------+ |OptimisationFile | File specifying some of the restart marker | | | offsets in each ImageFile | +-----------------------+---------------------------------------------------+ |AuthCode | Unknown | +-----------------------+---------------------------------------------------+ |SourceLens | Possibly the magnification | +-----------------------+---------------------------------------------------+ |PhysicalWidth | Width of the slide in some unit? | +-----------------------+---------------------------------------------------+ |PhysicalHeight | Height of the slide in some unit? | +-----------------------+---------------------------------------------------+ |LayerSpacing | Unknown | +-----------------------+---------------------------------------------------+ |MacroImage | Image file for the "macro" associated image | +-----------------------+---------------------------------------------------+ |PhysicalMacroWidth | Unknown | +-----------------------+---------------------------------------------------+ |PhysicalMacroHeight | Unknown | +-----------------------+---------------------------------------------------+ |XOffsetFromSlideCentre | Unknown | +-----------------------+---------------------------------------------------+ |YOffsetFromSlideCentre | Unknown | +-----------------------+---------------------------------------------------+ VMU File The .vmu file is the main index file for the VMU format. Only keys in the Uncompressed Virtual Microscope Specimen group are read by OpenSlide. Here are known keys from the file: +-----------------------+---------------------------------------------------+ |Key | Description | +-----------------------+---------------------------------------------------+ |NoLayers | (see VMS above) | +-----------------------+---------------------------------------------------+ |ImageFile | (see VMS above) | +-----------------------+---------------------------------------------------+ |ImageFile(x,y) | (see VMS above) | +-----------------------+---------------------------------------------------+ |ImageFile(z,x,y) | (see VMS above) | +-----------------------+---------------------------------------------------+ |MapFile | (see VMS above) | +-----------------------+---------------------------------------------------+ |MapScale | Seems to be the downsample factor of the map | +-----------------------+---------------------------------------------------+ |AuthCode | (see VMS above) | +-----------------------+---------------------------------------------------+ |SourceLens | (see VMS above) | +-----------------------+---------------------------------------------------+ |PixelWidth | Width of the image in pixels | +-----------------------+---------------------------------------------------+ |PixelHeight | Height of the image in pixels | +-----------------------+---------------------------------------------------+ |PhysicalWidth | (see VMS above) | +-----------------------+---------------------------------------------------+ |PhysicalHeight | (see VMS above) | +-----------------------+---------------------------------------------------+ |LayerSpacing | (see VMS above) | +-----------------------+---------------------------------------------------+ |LayerOffset | Unknown | +-----------------------+---------------------------------------------------+ |MacroImage | (see VMS above) | +-----------------------+---------------------------------------------------+ |PhysicalMacroWidth | (see VMS above) | +-----------------------+---------------------------------------------------+ |PhysicalMacroHeight | (see VMS above) | +-----------------------+---------------------------------------------------+ |XOffsetFromSlideCentre | (see VMS above) | +-----------------------+---------------------------------------------------+ |YOffsetFromSlideCentre | (see VMS above) | +-----------------------+---------------------------------------------------+ |Reference | Unknown | +-----------------------+---------------------------------------------------+ |BitsPerPixel | Bits per pixel, currently expected to be 36 | +-----------------------+---------------------------------------------------+ |PixelOrder | Currently expected to be RGB | +-----------------------+---------------------------------------------------+ |Creator | String describing the software creating this | | | image | +-----------------------+---------------------------------------------------+ |IlluminationMode | Unknown | +-----------------------+---------------------------------------------------+ |ExposureMultiplier | Unknown, possibly the multiplier used to scale to | | | 15 bits? | +-----------------------+---------------------------------------------------+ |GainRed | Unknown | +-----------------------+---------------------------------------------------+ |GainGreen | Unknown | +-----------------------+---------------------------------------------------+ |GainBlue | Unknown | +-----------------------+---------------------------------------------------+ |FocalPlaneTolerance | Unknown | +-----------------------+---------------------------------------------------+ |NMP | Unknown | +-----------------------+---------------------------------------------------+ |MacroIllumination | Unknown | +-----------------------+---------------------------------------------------+ |FocusOffset | Unknown | +-----------------------+---------------------------------------------------+ |RefocusInterval | Unknown | +-----------------------+---------------------------------------------------+ |CubeName | Unknown | +-----------------------+---------------------------------------------------+ |HardwareModel | Name of the hardware | +-----------------------+---------------------------------------------------+ |HardwareSerial | Serial number of the hardware | +-----------------------+---------------------------------------------------+ |NoFocusPoints | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint0X | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint0Y | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint0Z | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint1X | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint1Y | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint1Z | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint2X | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint2Y | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint2Z | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint3X | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint3Y | Unknown | +-----------------------+---------------------------------------------------+ |FocusPoint3Z | Unknown | +-----------------------+---------------------------------------------------+ |NoBlobPoints | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint0Blob | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint0FocusPoint | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint1Blob | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint1FocusPoint | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint2Blob | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint2FocusPoint | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint3Blob | Unknown | +-----------------------+---------------------------------------------------+ |BlobPoint3FocusPoint | Unknown | +-----------------------+---------------------------------------------------+ |BlobMapWidth | Unknown | +-----------------------+---------------------------------------------------+ |BlobMapHeight | Unknown | +-----------------------+---------------------------------------------------+ Optimisation File (only for VMS) The optimisation file contains a list of 32- (or 64- or 320- ?) bit little endian values, giving the file offset into an MCU row, each offset starts at a 40-byte alignment, and the last row (of the entire file, not each image) seems to be missing. The offsets are all packed into 1 file, even with multiple images. The order of images is left-to-right, top-to-bottom. Map File The VMS map file is a standard JPEG file. Its restart markers (if any) are not included in the optimisation file. The VMU map file is in NGR format. This file can be used to provide a lower-resolution view of the slide. Image Files These files are given by the various ImageFile keys. They are assumed to have a height which is a multiple of the MCU height. They are assumed to have a width which is a multiple of MCUs per row divided by the restart interval. For VMS, these files are in JPEG, for VMU they are in NGR format. NGR Format The NGR file contains uncompressed 16-bit RGB data, with a small header. The files we have encountered start with GN, two more bytes, and then width, height, and column width in little endian 32-bit format. The column width must divide evenly into the width. Column width is important, since NGR files are generated in columns, where the first column comes first in the file, followed by subsequent files. Columns are painted left-to-right. At offset 24 is another 32-bit integer which gives the offset in the file to the start of the image data. The image data we have encountered is in 16-bit little endian format. Associated Images macro the image file given by the MacroImage value in the VMS/VMU file Known Properties All key-value data stored in the VMS/VMU file are encoded as properties prefixed with "hamamatsu.". Test Data http://openslide.cs.cmu.edu/download/openslide-testdata/Hamamatsu/ (ndpi format, wrapped vms format, currently not readable by OpenSlide) http://openslide.cs.cmu.edu/download/openslide-testdata/Hamamatsu-vms/ (vms format) Preliminary NDPI Notes NDPI is basically VMS stuffed into a broken TIFF file. libtiff cannot read the headers of a TIFF file, because NDPI specifies the RowsPerStrip as the height of the file, and after doing out the multiplication, this typically overflows libtiff and it refuses to open the file. Also, the TIFF tags are not stored in sorted order (sometimes, they may have fixed this in later versions). Unlike the VMS format, the NDPI is stored in a pyramid format as TIFF directory entries. The macro image seems to come last. If one just reads the TIFF tags directly, perhaps using tiffdump, one will find: +----------------+---------------------------------------------------+ |Tag | Description | +----------------+---------------------------------------------------+ |ImageWidth | Width of the image | +----------------+---------------------------------------------------+ |ImageHeight | Height of the image | +----------------+---------------------------------------------------+ |Make | "Hamamatsu" | +----------------+---------------------------------------------------+ |Model | "NanoZoomer" or "C9600-12", etc | +----------------+---------------------------------------------------+ |XResolution | Seemingly correct X resolution, when interpreted | | | with ResolutionUnit | +----------------+---------------------------------------------------+ |YResolution | Seemingly correct Y resolution, when interpreted | | | with ResolutionUnit | +----------------+---------------------------------------------------+ |ResolutionUnit | Seemingly correct resolution unit | +----------------+---------------------------------------------------+ |Software | "NDP.scan", sometimes with a version number | +----------------+---------------------------------------------------+ |StripOffsets | The offset of the JPEG file for this layer | +----------------+---------------------------------------------------+ |StripByteCounts | The length of the JPEG file for this layer | +----------------+---------------------------------------------------+ |65420 | Unknown, always 1? | +----------------+---------------------------------------------------+ |65421 | Magnification? SourceLens from VMS? Seems | | | correctly downsampled for each entry. (-1 for | | | macro image, -2 for some sort of mask?) | +----------------+---------------------------------------------------+ |65422 | XOffsetFromSlideCentre | +----------------+---------------------------------------------------+ |65423 | YOffsetFromSlideCentre | +----------------+---------------------------------------------------+ |65424 | Unknown, always 0? | +----------------+---------------------------------------------------+ |65425 | Unknown, always 0? | +----------------+---------------------------------------------------+ |65426 | Optimisation entries, as above | +----------------+---------------------------------------------------+ |65428 | Unknown, AuthCode? | +----------------+---------------------------------------------------+ |65433 | Unknown, I have seen 1500 in this tag | +----------------+---------------------------------------------------+ |65439 | Unknown, perhaps some polygon ROI? | +----------------+---------------------------------------------------+ |65440 | Unknown, I have seen this: <0 0 0 1 0 2 0 3 0 4 0 | | | 5 0 6 0 7 0 8 1 9 1 10 1 11 1 12 1 13 1 14 1 15 1 | | | 16 1 17> | +----------------+---------------------------------------------------+ |65441 | Unknown, always 0? | +----------------+---------------------------------------------------+ |65442 | Seems to be Model | +----------------+---------------------------------------------------+ |65443 | Unknown, always 0? | +----------------+---------------------------------------------------+ |65444 | Unknown, always 80? | +----------------+---------------------------------------------------+ |65445 | Unknown, always 2? | +----------------+---------------------------------------------------+ |65446 | Unknown, always 0? | +----------------+---------------------------------------------------+ Unlike in VMS, JPEG files in NDPI are not necessarily valid. If ImageWidth or ImageHeight exceeds the JPEG limit of 65535, then the width or height as stored in the JPEG file is 0. JPEG files are not split into validly-sized files like in VMS. libjpeg will refuse to read the header of such a file, so the JPEG data stream must be altered when fed into libjpeg. Since a random access source manager is already required to read VMS JPEG files, this change is not too bad. APERIO FORMAT
Format single-file pyramidal tiled TIFF, with non-standard metadata and compression File extensions .svs, .tif OpenSlide vendor backend aperio OpenSlide ops backend tiff Vendor Documentation http://www.aperio.com/documents/api/Aperio_Digital_Slides_and_Third-party_data_interchange.pdf Detection Aperio slides are stored in single-file TIFF format. OpenSlide will detect a file as Aperio if: 1. The file is TIFF. 2. The ImageDescription tag starts with Aperio. Relevant TIFF tags +-----------------+-------------------------------------------------+ |Tag | Description | +-----------------+-------------------------------------------------+ |ImageDescription | Stores some important key-value pairs and other | | | information, see below | +-----------------+-------------------------------------------------+ |Compression | May be 33003 or 33005, which represent specific | | | kinds of JPEG 2000 compression, see below | +-----------------+-------------------------------------------------+ Extra data stored in ImageDescription For tiled images, the ImageDescription tag contains some dimensional downsample information as well as what look like offsets. Additionally, vertical line-delimited key-value pairs are stored, in at least the full-resolution image. A key-value pair is equals-delimited. These key-values are stored as properties starting with "aperio.". Currently, OpenSlide does not use any of the information present in these key-value fields. For stripped images, the ImageDescription tag may contain a name, followed by a carriage return. This is used for naming the associated images. The second image in the file does not have a name, though it is an associated image. TIFF Image Directory Organization http://www.aperio.com/documents/api/Aperio_Digital_Slides_and_Third-party_data_interchange.pdf page 14: The first image in an SVS file is always the baseline image (full resolution). This image is always tiled, usually with a tile size of 240x240 pixels. The second image is always a thumbnail, typically with dimensions of about 1024x768 pixels. Unlike the other slide images, the thumbnail image is always stripped. Following the thumbnail there may be one or more intermediate "pyramid" images. These are always compressed with the same type of compression as the baseline image, and have a tiled organization with the same tile size. Optionally at the end of an SVS file there may be a slide label image, which is a low resolution picture taken of the slide's label, and/or a macro camera image, which is a low resolution picture taken of the entire slide. The label and macro images are always stripped. JPEG 2000 (compression types 33003 or 33005) Some Aperio files use compression type 33003 or 33005. Images using this compression need to be decoded as a JPEG 2000 codestream. For 33003: YCbCr format, possibly with a chroma subsampling of 4:2:2. For 33005: RGB format. Note that the TIFF file may not encode the colorspace or subsampling parameters in the PhotometricInterpretation field, nor the YCbCrSubsampling field, even though the TIFF standard seems to require this. The correct subsampling can be found in the JPEG 2000 codestream. Associated Images thumbnail the second image in the file label optional, the name "label" is given in ImageDescription macro optional, the name "macro" is given in ImageDescription Known Properties All key-value data encoded in the ImageDescription TIFF field is represented as properties prefixed with "aperio.". Test Data http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/ MIRAX FORMAT
Format multi-file JPEG with very complicated proprietary metadata and indexes File extensions .mrxs OpenSlide vendor backend mirax OpenSlide ops backend jpeg Detection Note: MIRAX is incredibly complicated. These detection steps are probably not complete. OpenSlide will detect a file as MIRAX if: 1. The file ends with .mrxs. 2. A directory exists in the same location as the file, with the same name as the file minus the extension. 3. A file named Slidedat.ini exists in the directory. 4. The slidedat file is readable as a Windows INI-style file. 5. The slidedat file has a [GENERAL] section with the following keys: SLIDE_VERSION, SLIDE_ID, IMAGENUMBER_X, IMAGENUMBER_Y, CameraImageDivisionsPerSide. 6. The slidedat file has a [HIERARCHICAL] section with the following keys: HIER_COUNT, NONHIER_COUNT, INDEXFILE. 7. A key exists in the [HIERARCHICAL] section with the value of Slide zoom level. The key matches this printf-style template: HIER_%d_NAME. The %d is bound to the variable zoom_level. Currently, zoom_level must be 0. 8. The [HIERARCHICAL] section has a key with the name HIER_%d_COUNT where %d is the value of zoom_level in the previous step. The value must be an integer, interpreted as zoom_count. 9. Setting x to zoom_level and y from 0 to zoom_count, the [HIERARCHICAL] section has a key with the name HIER_x_VAL_y_SECTION. Let section_names[] be an array of length zoom_count, holding the values for each key. 10. The [DATAFILE] section must exist, with the following keys: FILE_COUNT. 11. There are FILE_COUNT keys in the [DATAFILE] section with the following names: FILE_%d, where %d goes from 0 to FILE_COUNT-1. 12. For each value in section_names, a group must exist with that name. Each group must contain the keys: OVERLAP_X, OVERLAP_Y, IMAGE_FILL_COLOR_BGR, DIGITIZER_WIDTH, DIGITIZER_HEIGHT. The overlap values must be parseable as doubles, the rest as integers. The key IMAGE_FORMAT must exist, with the value JPEG. 13. Each section_names section must have the key IMAGE_CONCAT_FACTOR. The value of the first section's IMAGE_CONCAT_FACTOR must be 0, the rest 1. 14. The [HIERARCHICAL] section has a key with the name NONHIER_%d_NAME (%d is an integer) and with the value VIMSLIDE_POSITION_BUFFER. Bind %d to the variable position_nonhier_offset. 15. The [HIERARCHICAL] section has a key with the name NONHIER_%d_NAME (%d is an integer) and with the value Scan data layer. Bind %d to the variable scan_nonhier_offset. 16. The [HIERARCHICAL] section has a key with the name NONHIER_%d_VAL_%d where the first %d is the value of scan_nonhier_offset. The key has a value of ScanDataLayer_SlideThumbnail. 17. The [HIERARCHICAL] section has a key with the name NONHIER_%d_VAL_%d where the first %d is the value of scan_nonhier_offset. The key has a value of ScanDataLayer_SlideBarcode. 18. The [HIERARCHICAL] section has a key with the name NONHIER_%d_VAL_%d where the first %d is the value of scan_nonhier_offset. The key has a value of ScanDataLayer_SlidePreview. 19. The value of the INDEXFILE key above is the name of a readable file. 20. The index file is of a valid format, and all data referred to by it is valid (see below). Overview Because JPEG does not allow for large files, multiple JPEG files are needed to encode large images. Unfortunately, (unlike TIFF) JPEG provides very poor support for random-access decoding of parts of a file. To avoid having many individual files, MIRAX packs JPEG files into a small number of data files. The index file provides offsets into the data files for each required piece of data. Index File The index file is a crazy beast. It starts with ASCII strings matching the SLIDE_VERSION and SLIDE_ID values from the slidedat file. Then, all hell breaks loose. The rest of the file consists of 32-bit little-endian integers (unaligned) with seemingly no structure. More info coming, for now see misc/print-mirax.py[2]. Data Files Slide Position File Associated Images Known Properties Test Data http://openslide.cs.cmu.edu/download/openslide-testdata/Mirax/ GENERIC TILED TIFF FORMAT
Format single-file pyramidal tiled TIFF File extensions .tif OpenSlide vendor backend generic-tiff OpenSlide ops backend tiff Detection OpenSlide will detect a file as generic TIFF if: 1. No other detections succeed. 2. The file is TIFF. 3. The initial image is tiled. TIFF Image Directory Organization The first image in the TIFF file is the full-resolution image. Any other tiled images in the file with the "reduced resolution" bit set are assumed to be reduced-resolution versions of the original. Associated Images None. Known Properties Many TIFF tags are encoded as properties starting with "tiff.". AUTHORS
The Carnegie Mellon School of Computer Science. This manual page was written by Mathieu Malaterre <mathieu.malaterre@gmail.com> for the Debian GNU/Linux system (but may be used by others). NOTES
1. Supported Virtual Slide Formats http://openslide.org/Supported%20Virtual%20Slide%20Formats 2. misc/print-mirax.py http://github.com/openslide/openslide/blob/master/misc/print-mirax.py OpenSlide 3.2.5 01/16/2012 OPENSLIDE-SHOW-PRO(1)
Man Page

Featured Tech Videos