The H5RA Interface is strictly experimental at this time;
the interface may change dramatically or support for ragged arrays
may be unavailable in future in releases. As a result, future releases
may be unable to retrieve data stored with this interface.
Do not create any archives using this interface! |
---|
Ragged arrays should be considered alpha quality. They were added to HDF5 to satisfy the needs of the ASCI/DMF vector bundle project; the interface and storage methods are likely to change in the future in ways that are not backward compatible.
A two-dimensional ragged array has been added to the library and built on top of other existing functionality. A ragged array is a one-dimensional array of rows where the length of any row is independent of the lengths of the other rows. The number of rows and the length of each row can be changed at any time (the current version does not support truncating an array by removing rows). All elements of the ragged array have the same data type and, as with datasets, the data is type-converted between memory buffers and files.
The current implementation works best when most of the rows are approximately the same length since a two dimensional dataset can be created to hold a nominal number of elements from each row with the additional elements stored in a separate dataset which implements a heap.
A ragged array is a composite object implemented as a group with three datasets. The name of the group is the name of the ragged array. The raw dataset is a two-dimensional array that contains the first N elements of each row where N is determined by the application when the array is created. If most rows have fewer than N elements then internal fragmentation may be quite bad.
The over dataset is a one-dimensional array that contains elements from each row that don't fit in the raw dataset.
The meta dataset maintains information about each row such as the number of elements in the row, the location of the overflow elements in the over dataset (if any), and the amount of space reserved in over for the row. The meta dataset has one entry per row and is where most of the storage overhead is concentrated when rows are relatively short.
hid_t H5RAcreate (hid_t location, const char
*name, hid_t type, hid_t
plist)
hid_t H5RAopen (hid_t location, const char
*name)
herr_t H5RAclose (hid_t array)
In order to be as efficient as possible the ragged array layer operates on sets of contiguous rows and it is to the application's advantage to perform I/O on as many rows at a time as possible. These functions take a starting row number and the number of rows on which to operate.
herr_t H5RAwrite (hid_t array_id, hssize_t
start_row, hsize_t nrows, hid_t
type, hsize_t size[], void
*buf[])
herr_t H5RAread (hid_t array_id, hssize_t
start_row, hsize_t nrows, hid_t
type, hsize_t size[], void
*buf[])