From 91709a2b438aa622f0fef679e7c05378b07adecb Mon Sep 17 00:00:00 2001 From: Quincey Koziol Date: Wed, 10 Sep 2003 10:30:32 -0500 Subject: [svn-r7452] Purpose: Checkpoint file format spec. --- doc/html/H5.format.html | 318 +++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 273 insertions(+), 45 deletions(-) diff --git a/doc/html/H5.format.html b/doc/html/H5.format.html index c9bbd5e..2b849f8 100644 --- a/doc/html/H5.format.html +++ b/doc/html/H5.format.html @@ -105,8 +105,8 @@ TABLE.list TD { border:none; }
  • Name: Simple Dataspace
  • Name: Datatype -
  • Name: Data Storage - Fill Value -
  • Name: Reserved - not assigned yet +
  • Name: Data Storage - Fill Value (Old) +
  • Name: Data Storage - Fill Value @@ -1701,7 +1701,7 @@ TABLE.list TD { border:none; } - Collection Size + Collection SizeL @@ -1724,6 +1724,14 @@ TABLE.list TD { border:none; }
    Global Heap Object 0 (free space)

    + + + +
    + (Items marked with an 'L' the above table are +
    + of the size specified in "Size of Lengths.") +

    @@ -1758,7 +1766,7 @@ TABLE.list TD { border:none; } - Collection Data Size + Collection Size

    This is the size in bytes of the entire collection including this field. The default (and minimum) @@ -1815,7 +1823,7 @@ TABLE.list TD { border:none; } - Object Data SizeL + Object SizeL @@ -1875,9 +1883,9 @@ TABLE.list TD { border:none; } Object Size -

    This is the size of the the fields above plus the object data - stored for the object. The actual storage size is rounded up to a - multiple of eight. +

    This is the size of the object data stored for the object. + The actual storage space allocated for the object data is rounded + up to a multiple of eight.

    @@ -2025,7 +2033,8 @@ TABLE.list TD { border:none; } integrity. Information stored by user applications as attributes is also stored in the object's header. The header of each object is not necessarily located immediately prior to the object's data in the - file and in fact may be located in any position in the file. + file and in fact may be located in any position in the file. The order + of the messages in an object header is not significant.

    Header messages are aligned on 8-byte boundaries. @@ -2904,6 +2913,7 @@ TABLE.list TD { border:none; } +

    Class specific information for Fixed-Point Numbers (Class 0): @@ -4146,69 +4156,287 @@ TABLE.list TD { border:none; }

    -

    Name: Data Storage - Fill Value

    - Header Message Type: 0x0004
    - Length: varies
    - Status: Optional, may not be repeated.
    +

    Name: Data Storage - Fill Value (Old)

    + +

    Header Message Type: 0x0004 +

    +

    Length: varies +

    +

    Status: Optional, may not be repeated. +

    -

    The fill value message stores a single data point value which - is returned to the application when an uninitialized data point - is read from the dataset. The fill value is interpretted with - the same datatype as the dataset. If no fill value message is - present then a fill value of all zero is assumed. +

    Description: The fill value message stores a single + data value which is returned to the application when an uninitialized + data element is read from a dataset. The fill value is interpreted + with the same datatype as the dataset. If no fill value message is + present then a fill value of all zero bytes is assumed. +

    -

    -

    - -
    - Fill Value Message +

    This fill value message is deprecated in favor of the "new" + fill value message (Message Type 0x0005) and is only written to the + file for forward compatibility with versions of the HDF5 library before + the 1.6.0 version. Additionally, it only appears for datasets with a + user defined fill value (as opposed to the library default fill value + or an explicitly set "undefined" fill value). +

    + +

    Format of Data: +
    +

    + + - + - - + + - +
    + Fill Value Message (Old)
    byte byte byte byte
    Size (4 bytes)
    Size

    Fill Value
    - +
    -

    -

    - - - - +
    +
    +
    Field NameDescription
    + + + - - - + + + - + - +
    Field NameDescription
    Size (4 bytes)This is the size of the Fill Value field in bytes.
    Size +

    This is the size of the Fill Value field in bytes. +

    +
    Fill ValueThe fill value. The bytes of the fill value are - interpreted using the same datatype as for the dataset. +

    The fill value. The bytes of the fill value are interpreted + using the same datatype as for the dataset. +

    +
    -
    + +

    -

    Name: Reserved - Not Assigned Yet

    - Header Message Type: 0x0005
    - Length: N/A
    - Status: N/A
    +

    Name: Data Storage - Fill Value

    + +

    Header Message Type: 0x0005 +

    +

    Length: varies +

    +

    Status: Required for dataset objects, may not be repeated. +

    +

    Description: The fill value message stores a single + data value which is returned to the application when an uninitialized + data element is read from a dataset. The fill value is interpreted + with the same datatype as the dataset. +

    +

    Format of Data: +
    +

    + + + + + + + + + + + + + + + + + + + + + + + + +
    + Fill Value Message +
    bytebytebytebyte
    VersionSpace Allocation TimeFill Value Write TimeFill Value Defined
    Size

    Fill Value

    +
    + +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Field NameDescription
    Version +

    The version number information is used for changes in the + format of the fill value message and is described here: + + + + + + + + + + + + + + + + + + +
    VersionDescription
    0Never used +
    1Used by version 1.6.x of the library to encode + fill values. In this version, the Size field is + always present. +
    2The current version used by the library (version + 1.7.3 or later). In this version, the Size field is + only present if the Fill Value Defined field is set + to 1. +
    +

    +
    Space Allocation Time +

    When the storage space for the dataset's raw data will be + allocated. The allowed values are: + + + + + + + + + + + + + + + + + + +
    ValueDescription
    1Early allocation. Storage space for the entire dataset + should be allocated in the file when the dataset is + created. +
    2Late allocation. Storage space for the entire dataset + should not be allocated until the dataset is written + to. +
    3Incremental allocation. Storage space for the + dataset should not be allocated until the portion + of the dataset is written to. This is currently + used in conjunction with chunked data storage for + datasets. +
    +

    +
    Fill Value Write Time +

    At the time that storage space for the dataset's raw data is + allocated, this value indicates whether the fill value should + be written to the raw data storage elements. The allowed values + are: + + + + + + + + + + + + + + + + + + +
    ValueDescription
    0On allocation. The fill value is always written to + the raw data storage when the storage space is allocated. +
    1Never. The fill value should never be written to + the raw data storage. +
    2Fill value written if set by user. The fill value + will be written to the raw data storage when the storage + space is allocated only if the user explicitly set + the fill value. If the fill value is the library + default or is undefined, it will not be written to + the raw data storage. +
    +

    +
    Fill Value Defined +

    This value indicates if a fill value is defined for this + dataset. If this value is 0, the fill value is undefined. + If this value is 1, a fill value is defined for this dataset. + For version 2 or later of the fill value message, this value + controls the presence of the Size field. +

    +
    Size +

    This is the size of the Fill Value field in bytes. This field + is not present if the Version field is >1 and the Fill Value + Defined field is set to 0. +

    +
    Fill Value +

    The fill value. The bytes of the fill value are interpreted + using the same datatype as for the dataset. +

    +
    +
    +

    Name: Data Storage - Compact

    -- cgit v0.12