Hi,
h5dump dumps just everything, so it remembers how it found each component.
Scanning an entire file for a particular information, whether it be a
dataset
or a named datatype, is of course inefficient.
Do you have any control about how the file is written or any knowledge
about the file layout that may help you to predict in advance where
the named data type might be? What are you planning to do with the
named data type?
Werner
On Wed, 13 Apr 2011 07:40:59 -0500, Bernd Rinn <[email protected]>
wrote:
Hi,
Consider I have a dataset that uses a committed (named) datatype, what
is the most efficient way to find the path of this datatype in an HDF5
file? Looking at the the API calls in H5T, the only way I can see is to
scan all groups for committed datasets and calling H5Tequal() on each of
them to find out whether this one equals the datatype of the dataset.
The scanning might be very inefficient if the HDF5 file contains many
groups with many members. Is there a more efficient way of doing that?
How does h5dump get the information that it prints in the "DATATYPE"
line for a dataset?
Bernd
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
--
___________________________________________________________________________
Dr. Werner Benger Visualization Research
Laboratory for Creative Arts and Technology (LCAT)
Center for Computation & Technology at Louisiana State University (CCT/LSU)
211 Johnston Hall, Baton Rouge, Louisiana 70803
Tel.: +1 225 578 4809 Fax.: +1 225 578-5362
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
