Commit Graph

6 Commits

Author SHA1 Message Date
Paul Harten
2aefbf7603 [svn-r1004] Purpose:
Conform closer to other test print-out.

Solution:
    Added "All h5dump tests passed." statement to output
    of testh5dump.sh when appropriate.  Similarly, added
    "All h5toh4 tests passed." statement to output of
    testh5toh4 when appropriate.

    Also, added the testing of converting H5 files with
    loop pathways into H4 files with recursive references.

Platforms tested:
    Solaris2.5, Digital Unix 4.0
1999-01-05 14:40:32 -05:00
Paul Harten
01eb265261 [svn-r1000] Purpose:
Conform closer to other test print-out.

Problem:
    Multiple "PASSED" statements for single test results when test involves
    conversion of multiple files.  Should be single "PASSED" statement for
    test results.

Solution:
    "*FAILED*" statement given if conversion fails for any file.  Differences
    given between expected results and actual results for each file that fails.
    "PASSED" statement given when conversion is successful for all files.

Platform tested:
    Solaris2.5
1998-12-30 16:15:03 -05:00
Paul Harten
a88aa59718 [svn-r988] Purpose:
New feature, Documentation

Solution:
    Changed h5toh4 testing output to more closely resemble other HDF5
    testing output.
    Also added documentation to describe the puposes of the
    conversion test files.

Platform tested:
    Solaris2.5
1998-12-22 13:36:19 -05:00
Paul Harten
caeb6c614f [svn-r978] Purpose: Bug fixes
Problems:
    There were three separate bugs in the h5toh4 converter worked on.
    They were:

    1) When a loop was detected, the H4 file was missing references
    to paths which were available in the H5 file.

    2) When an H4 SDS or Vdata was created from a H5 dataset, the H4
    object was referenced in the root group, instead of the correct
    Vgroup.

    3) The FIRST path taken to an object for the h5toh4 conversion
    could not involve a SOFTLINK.

Solutions:
    The bug fixes were:

    1) All of the associated references to available paths which
    occur in the H5 file, now appear in the H4 file.

    2) After an H4 SDS or Vdata is created from a H5 dataset, the H4
    object is tag/ref'ed in the appropriate Vgroup.

    3) The FIRST path taken to an H5 object for the H5toh4 conversion
    may involve a HARDLINK, a SOFTLINK, or neither.  The same is
    true of any additional paths to the same object.

Platform tested:
    Solaris2.5
1998-12-20 23:05:28 -05:00
Paul Harten
bdc304d612 [svn-r958] Purpose:
New feature

Solution:
    Testing of Extendable Dataset support in h5toh4 converter when
    extendable dimension is first dimension.

Platform tested:
    Solaris2.5
1998-12-01 16:56:14 -05:00
Paul Harten
6987a7dee5 [svn-r939] Purpose:
New Feature

Solution:
    This is a tester for the h5toh4 converter.  It is implemented
    on different HDF5 files to produce HDF4 files.  After each HDF4
    file is produced,  the file is run through the HDF4 dumper hdp.
    The dumper results are compared with expected results and any
    differences are noted.

    Note: The "/hdf4/bin" directory needs to be part of the tester's
    $PATH.

Platform tested:
    Solaris2.5, HP10.20
1998-11-21 15:00:58 -05:00