diff options
| author | Frank Baker <fbaker@hdfgroup.org> | 2005-07-19 17:28:56 (GMT) |
|---|---|---|
| committer | Frank Baker <fbaker@hdfgroup.org> | 2005-07-19 17:28:56 (GMT) |
| commit | 794ba0a251af47b8e3c60afa2fe92d267e2a6b55 (patch) | |
| tree | f24cea3b81ff02fa3f31c0a1c4e80fa10f4393c0 /doc/html/TechNotes/TestReview | |
| parent | d2e92fd23610c3ccdddbbc55484e54a5a21a9252 (diff) | |
| download | hdf5-794ba0a251af47b8e3c60afa2fe92d267e2a6b55.zip hdf5-794ba0a251af47b8e3c60afa2fe92d267e2a6b55.tar.gz hdf5-794ba0a251af47b8e3c60afa2fe92d267e2a6b55.tar.bz2 | |
[svn-r11084]
Description:
All HDF5 user documentation has been moved to a separate hdf5doc/
repository, managed under Subversion.
With this 'cvs commit', all files are stripped from hdf5/doc/.
THIS CHANGE IS APPLIED ONLY TO THE HDF5 DEVELOPMENT BRANCH,
post Release 1.6.x; it is not applied to the release branches.
Diffstat (limited to 'doc/html/TechNotes/TestReview')
| -rw-r--r-- | doc/html/TechNotes/TestReview/H5Dget_offset.html | 199 | ||||
| -rw-r--r-- | doc/html/TechNotes/TestReview/H5Tget_native_type.html | 522 |
2 files changed, 0 insertions, 721 deletions
diff --git a/doc/html/TechNotes/TestReview/H5Dget_offset.html b/doc/html/TechNotes/TestReview/H5Dget_offset.html deleted file mode 100644 index 0056f00..0000000 --- a/doc/html/TechNotes/TestReview/H5Dget_offset.html +++ /dev/null @@ -1,199 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML> -<HEAD> - <TITLE>H5Dget_offset Test Review</TITLE> - <META http-equiv="content-type" content="text/html; charset=ISO-8859-1"> - <META name="author" content="Quincey Koziol"> -</HEAD> -<body text="#000000" bgcolor="#FFFFFF"> -<STYLE type="text/css"> -OL.loweralpha { list-style-type: lower-alpha } -OL.upperroman { list-style-type: upper-roman } -</STYLE> - -<CENTER><H1>H5Dget_offset Test Review</H1></CENTER> - -<OL class="upperroman"> - -<LI><H3><U>Purpose:</U></H3> -<P>This document describes the API test review results for <a href="../../RM_H5D.html#Dataset-GetOffset">H5Dget_offset</a>(). -</P> - -<LI><H3><U>Serial Review:</U></H3> -<TABLE border="1"> -<TR> -<TH>Test case -</TH> - -<TH>Test source file -</TH> - -<TH>Test method -</TH> - -<TH>Expected test results -</TH> - -<TH>Notes -</TH> - -<TR> -<TD>Chunked dataset -</TD> - -<TD>dsets.c -</TD> - -<TD> -<OL> -<LI>Create chunked dataset -<LI>Query dataset offset -</OL> -</TD> - -<TD>FAIL -</TD> - -<TD> -<P>Because dataset is stored in chunks that are indexed by a B-tree, there is -no single piece of data to query the offset of. -</P> -<P>It may be possible in the future to -enhance this function by querying the offset of a particular chunk (or chunks), -but that has limited use because chunks could be compressed, etc. with an I/O -filter. -</P> -</TD> - -</TR> - -<TR> -<TD>Compact dataset -</TD> - -<TD>dsets.c -</TD> - -<TD> -<OL> -<LI>Create chunked dataset -<LI>Query dataset offset -</OL> -</TD> - -<TD>FAIL -</TD> - -<TD> -<P>Because dataset is stored in the object header of the dataset, there is -no separate piece of data to query the offset of. -</P> -<P>It may be possible in the future to get the offset of the data in the object -header, but this is problematic due to the fact that the messages in the object -header can get relocated in the file when changes (like adding attributes, etc.) -are made to the dataset, invalidating the address given to the user. -filter. -</P> -</TD> - -</TR> - -<TR> -<TD>Contiguous dataset, [user block size] == 0, not external -</TD> - -<TD>dsets.c -</TD> - -<TD> -<OL> -<LI>Create file with 0 sized user-block (the default) -<LI>Create contigous dataset -<LI>Query dataset offset -</OL> -</TD> - -<TD> -<P>Succeed in getting the proper address and be able to verify -that the data at that address in the file is what was written out. -</P> -<P>When data storage allocation is "late" (the default), querying the offset -should fail if performed before data is written to the dataset. -</P> -</TD> - -<TD>Needs additional test to verify that the data written out is located at the -correct offset in the file. -</TD> - -</TR> - -<TR> -<TD>Contiguous dataset, [user block size] != 0, not external -</TD> - -<TD>dsets.c -</TD> - -<TD> -<OL> -<LI>Create file with non-0 sized user-block -<LI>Create contigous dataset -<LI>Query dataset offset -</OL> -</TD> - -<TD> -<P>Succeed in getting the proper address and be able to verify -that the data at that address in the file is what was written out. -</P> -<P>When data storage allocation is "late" (the default), querying the offset -should fail if performed before data is written to the dataset. -</P> -</TD> - -<TD>Needs test for this case. -</TD> - -</TR> - -<TR> -<TD>Contiguous dataset, [user block size] == 0, external data storage -</TD> - -<TD>external.c -</TD> - -<TD> -<OL> -<LI>Create contigous dataset with external storage -<LI>Query dataset offset -</OL> -</TD> - -<TD>FAIL -</TD> - -<TD> -<P>In theory, it's easy to return the offset of the data in the external file, -but this wasn't done because it would be too easy for users to assume that the -offset returned was in the HDF5 file instead of the external file. -</P> -</TD> - -</TR> - -</TABLE> -<BR> - -<LI><H3><U>Parallel Review:</U></H3> -<P>The H5Dget_offset() function is not tested in parallel. Currently, there -does not appear to be a need for this. -</P> - - -</OL> - -</BODY> -</HTML> - diff --git a/doc/html/TechNotes/TestReview/H5Tget_native_type.html b/doc/html/TechNotes/TestReview/H5Tget_native_type.html deleted file mode 100644 index 1c6409d..0000000 --- a/doc/html/TechNotes/TestReview/H5Tget_native_type.html +++ /dev/null @@ -1,522 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML> -<HEAD> - <TITLE>H5Dget_native_type Test Review</TITLE> - <META http-equiv="content-type" content="text/html; charset=ISO-8859-1"> - <META name="author" content="Quincey Koziol"> -</HEAD> -<body text="#000000" bgcolor="#FFFFFF"> -<STYLE type="text/css"> -OL.loweralpha { list-style-type: lower-alpha } -OL.upperroman { list-style-type: upper-roman } -</STYLE> - -<CENTER><H1>H5Dget_native_type Test Review</H1></CENTER> - -<OL class="upperroman"> - -<LI><H3><U>Purpose:</U></H3> -<P>This document describes the API test review results for <a href="../../RM_H5T.html#Datatype-GetNativeType">H5Dget_native_type</a>(). -</P> - -<LI><H3><U>Serial Review:</U></H3> -<TABLE border="1"> -<TR> -<TH>Test case -</TH> - -<TH>Test source file -</TH> - -<TH>Test method -</TH> - -<TH>Expected test results -</TH> - -<TH>Notes -</TH> - -<TR> -<TD>Native int datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create dataset with I32BE datatype -<LI>Query dataset's datatype -<LI>Create native datatype from dataset datatype -<LI>Compare order, class & size of native datatype to known results -</OL> -</TD> - -<TD>Check that type's size, order and class are correct. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P>It would be convenient to have a function in the test module for choosing -the correct atomic datatype based on the particular platform settings. This -should use the H5_SIZEOF_<foo> macros. -</P> -</TD> - -</TR> - -<TR> -<TD>Native long long datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create dataset with I64LE datatype -<LI>Query dataset's datatype -<LI>Create native datatype from dataset datatype -<LI>Compare order, class & size of native datatype to known results -</OL> -</TD> - -<TD>Check that type's size, order and class are correct. -</TD> - -<TD> -<P>Data is NOT written & read back in for this test. -</P> -</TD> - -</TR> - -<TR> -<TD>Native char datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create dataset with I8LE datatype -<LI>Query dataset's datatype -<LI>Create native datatype from dataset datatype -<LI>Compare order, class & size of native datatype to known results -</OL> -</TD> - -<TD>Check that type's size, order and class are correct. -</TD> - -<TD> -<P>Data is NOT written & read back in for this test. -</P> -</TD> - -</TR> - -<TR> -<TD>Native float datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create dataset with F32BE datatype -<LI>Query dataset's datatype -<LI>Create native datatype from dataset datatype -<LI>Compare order, class & size of native datatype to known results -</OL> -</TD> - -<TD>Check that type's size, order and class are correct. -</TD> - -<TD> -<P>Data is NOT written & read back in for this test. -</P> -<P>Need test for native double datatype (stored as 32-bit floating-point -datatype in file). This will probably require using an "epsilon" if the data -is compared for this test. -</P> -</TD> - -</TR> - -<TR> -<TD>Compound datatype with atomic fields -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create datatype describing native (unpacked) struct in memory -<LI>Create datatype describing packed struct for disk -<LI>Create dataset with "packed" compound datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the native, -unpacked datatype. -</OL> -</TD> - -<TD>Check that native and unpacked datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -</TD> - -</TR> - -<TR> -<TD>Compound datatype with one compound field -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create datatype describing nested native (unpacked) structs in memory -<LI>Create datatype describing nested packed structs for disk -<LI>Create dataset with "packed" compound datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the native, -unpacked datatype. -</OL> -</TD> - -<TD>Check that native and unpacked datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P>Could use test for compound datatype with multiple compound fields. -</P> -<P>Could use test for 3 or more nested deep compound datatype. -</P> -</TD> - -</TR> - -<TR> -<TD>Enum datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create enum datatype -<LI>Create dataset with enum datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -enum datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -</TD> - -</TR> - -<TR> -<TD>Array datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create array datatype -<LI>Create dataset with array datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -array datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P><EM>This is not tested currently.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>Array of compound datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create array of compound datatype -<LI>Create dataset with array of compound datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -array of compound datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -</TD> - -</TR> - -<TR> -<TD>Compound datatype with array field -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create compound datatype with array field -<LI>Create dataset with compound datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -compound datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P><EM>This is not tested currently.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>VL datatype with atomic base type -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create VL datatype -<LI>Create dataset with VL datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -VL datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P><EM>Combinations with VL datatypes in other composite types and with other -datatypes for the base type of the VL datatype are not tested.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>VL string datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create VL string datatype -<LI>Create dataset with VL string datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -VL string datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P><EM>Combinations with VL string datatypes in composite types -are not tested.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>Reference datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create reference datatype -<LI>Create dataset with reference datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -reference datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P><EM>Combinations with reference datatypes in composite types -are not tested.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>Opaque datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create opaque datatype -<LI>Create dataset with opaque datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -opaque datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P><EM>Combinations with opaque datatypes in composite types -are not tested.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>Bitfield datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create bitfield datatype -<LI>Create dataset with bitfield datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -bitfield datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P>Data is written & read back in for this test. -</P> -<P><EM>Combinations with bitfield datatypes in composite types -are not tested.</EM> -</P> -</TD> - -</TR> - -<TR> -<TD>Time datatype -</TD> - -<TD>native.c -</TD> - -<TD> -<OL> -<LI>Create time datatype -<LI>Create dataset with time datatype -<LI>Query dataset's datatype -<LI>Get native datatype from dataset's datatype -<LI>Use H5Tequal to verify that the native datatype is the same as the original -time datatype. -</OL> -</TD> - -<TD>Check that native and original datatypes are equal. -</TD> - -<TD> -<P><EM>This is not tested currently.</EM> -</P> -</TD> - -</TR> - -</TABLE> -<BR> - -<LI><H3><U>Parallel Review:</U></H3> -<P>The H5Dget_native_type() function is not tested in parallel. Currently, -there does not appear to be a need for this. -</P> - - -</OL> - -</BODY> -</HTML> - |