Sets up use of the SZIP compression filter
H5P_SET_SZIP ( plist, options_mask, pixels_per_block )
herr_t H5Pset_szip(hid_t plist, unsigned int options_mask, unsigned int pixels_per_block)
Fortran90 Interface: h5pset_szip_f SUBROUTINE h5pset_szip_f(prp_id, options_mask, pixels_per_block, hdferr) IMPLICIT NONE INTEGER(HID_T), INTENT(IN) :: prp_id ! Dataset creation property list identifier INTEGER, INTENT(IN) :: options_mask ! A bit-mask conveying the desired ! SZIP options ! Current valid values in Fortran are: ! H5_SZIP_EC_OM_F ! H5_SZIP_NN_OM_F INTEGER, INTENT(IN) :: pixels_per_block ! The number of pixels or data elements ! in each data block INTEGER, INTENT(OUT) :: hdferr ! Error code ! 0 on success and -1 on failure END SUBROUTINE h5pset_szip_f
|hid_t ||IN: Dataset creation property list identifier|
|unsigned int |
IN: A bit-mask conveying the desired SZIP options
Valid values are
|unsigned int ||IN: The number of pixels or data elements in each data block|
H5P_SET_SZIP sets an SZIP compression filter,
H5Z_FILTER_SZIP, for a dataset. SZIP is a compression method designed for use with scientific data.
Before proceeding, all users should review the “Limitations” section below.
Users familiar with SZIP outrside the HDF5 context may benefit from reviewing “Notes for Users Familiar with SZIP in Other Contexts” below.
In the text below, the term pixel refers to an HDF5 data element. This terminology derives from SZIP compression's use with image data, where pixel referred to an image pixel.
bits_per_pixel value (see Notes, below) is automatically set, based on the HDF5 datatype. SZIP can be used with atomic datatypes that may have size of 8, 16, 32, or 64 bits. Specifically, a dataset with a datatype that is 8-, 16-, 32-, or 64-bit signed or unsigned integer; char; or 32- or 64-bit float can be compressed with SZIP. See Notes, below, for further discussion of the the SZIP
SZIP options are passed in an options mask,
options_mask, as follows.
(Mutually exclusive; select one.)
|Selects entropy coding method.|
Selects nearest neighbor coding method.
The following guidelines can be used in determining which option to select:
- The entropy coding method, the EC option specified by
H5_SZIP_EC_OPTION_MASK, is best suited for data that has been processed. The EC method works best for small numbers.
- The nearest neighbor coding method, the NN option specified by
H5_SZIP_NN_OPTION_MASK, preprocesses the data then the applies EC method as above.
Other factors may affect results, but the above criteria provides a good starting point for optimizing data compression.
SZIP compresses data block by block, with a user-tunable block size. This block size is passed in the parameter
pixels_per_block and must be even and not greater than 32, with typical values being
32. This parameter affects compression ratio; the more pixel values vary, the smaller this number should be to achieve better performance.
In HDF5, compression can be applied only to chunked datasets. If
pixels_per_block is bigger than the total number of elements in a dataset chunk,
H5P_SET_SZIP will succeed but the subsequent call to
H5D_CREATE will fail; the conflict can be detected only when the property list is used.
To achieve optimal performance for SZIP compression, it is recommended that a chunk's fastest-changing dimension be equal to N times
pixels_per_block where N is the maximum number of blocks per scan line allowed by the SZIP library. In the current version of SZIP, N is set to 128.
SZIP compression is an optional HDF5 filter.
- SZIP compression cannot be applied to compound, array, variable-length, enumeration, or any other user-defined datatypes.
If an SZIP filter is set in a dataset creation property list used to create a dataset containing a non-allowed datatype, the call to
H5D_CREATEwill fail; the conflict can be detected only when the property list is used.
Notes for Users Familiar with SZIP in Other Contexts:
The following notes are of interest primarily to those who have used SZIP compression outside of the HDF5 context.
In non-HDF5 applications, SZIP typically requires that the user application supply additional parameters:
pixels_in_object, the number of pixels in the object to be compressed
bits_per_pixel, the number of bits per pixel
pixels_per_scanline, the number of pixels per scan line
These values need not be independently supplied in the HDF5 environment as they are derived from the datatype and dataspace, which are already known. In particular, HDF5 sets
pixels_in_object to the number of elements in a chunk and
bits_per_pixel to the size of the element or pixel datatype. The following algorithm is used to set
- If the size of a chunk's fastest-changing dimension, size, is greater than 4K, set
pixels_per_scanlineto 128 times
- If size is less than 4K but greater than
pixels_per_scanlineto the minimum of size and 128 times
- If size is less than
pixels_per_blockbut greater than the number elements in the chunk, set
pixels_per_scanlineto the minimum of the number elements in the chunk and 128 times
The HDF5 datatype may have precision that is less than the full size of the data element, e.g., an 11-bit integer can be defined using
H5T_SET_PRECISION. To a certain extent, SZIP can take advantage of the precision of the datatype to improve compression:
- If the HDF5 datatype size is 24-bit or less and the offset of the bits in the HDF5 datatype is zero (see
H5T_GET_OFFSET), the data is the in lowest N bits of the data element. In this case, the SZIP
bits_per_pixelis set to the precision of the HDF5 datatype.
- If the offset is not zero, the SZIP
bits_per_pixelwill be set to the number of bits in the full size of the data element.
- If the HDF5 datatype precision is 25-bit to 32-bit, the SZIP
bits_per_pixelwill be set to 32.
- If the HDF5 datatype precision is 33-bit to 64-bit, the SZIP
bits_per_pixelwill be set to 64.
HDF5 always modifies the options mask provided by the user to set up usage of
ALLOW_K13_OPTION_MASK, and one of
MSB_OPTION_MASK, depending on endianness of the datatype.
|1.6.0||Function introduced in this release.|