summaryrefslogtreecommitdiffstats
path: root/tools/testfiles/tnbit.ddl
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r14905] Introduced a ratio formula compression ratio = uncompressed ↵Pedro Vicente Nunes2008-05-011-1/+1
| | | | | | | | size / compressed size in the printing of the compression with 3 digits of precision per hdf-forum NASA developers suggestion tested: windows, linux, solaris
* [svn-r14903] Undoing change committed in r14902.Scot Breitenfeld2008-04-301-1/+1
|
* [svn-r14902] Merged fortran_1_8 branch changes r14505:14901 into the trunk. ↵Scot Breitenfeld2008-04-301-1/+1
| | | | New fortran wrappers added.
* [svn-r14892] RFC display compression ratio in h5dumpPedro Vicente Nunes2008-04-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here's the current behavior of h5dump regarding the printing of the dataset creation property list For example ./h5dump -H -p -d filters HDF5 "tfilters.h5" { DATASET "deflate" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 20, 10 ) / ( 20, 10 ) } STORAGE_LAYOUT { CHUNKED ( 10, 5 ) SIZE 385 } FILTERS { COMPRESSION DEFLATE { LEVEL 9 } } FILLVALUE { FILL_TIME H5D_FILL_TIME_IFSET VALUE 0 } ALLOCATION_TIME { H5D_ALLOC_TIME_INCR } } } The proposed behavior is to add this information after SIZE SIZE 385 (51.9%COMPRESSION) That percentage is obtained trough Per = (b-a) / a Where a = theoretical size obtained by multiplying datum size times number of elements b = size obtained with H5Dget_storage_size The final print would look like HDF5 "tfilters.h5" { DATASET "deflate" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 20, 10 ) / ( 20, 10 ) } STORAGE_LAYOUT { CHUNKED ( 10, 5 ) SIZE 385 (51.9%COMPRESSION) } FILTERS { COMPRESSION DEFLATE { LEVEL 9 } } FILLVALUE { FILL_TIME H5D_FILL_TIME_IFSET VALUE 0 } ALLOCATION_TIME { H5D_ALLOC_TIME_INCR } } } tested: windows, linux, solaris
* [svn-r12171] Purpose:Pedro Vicente Nunes2006-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | bug fixes Description: h5dump/h5ls were not displaying long doubles correctly Solution: 1) the print datatype functions were incorrectly testing for the valid return value from H5Tequal, (TRUE), causing the display of an incorrect name of a dataype in error cases from H5Tequal 2) h5tools_print_str did not have a case for native long double 3) added a file generator for a long double dataset 4) added one script test for the long double data (commented , some sytems don't have a native long double match, and the output differs) 5) added a vms file and h5dump script test Platforms tested: linux 32, 64 solaris AIX Misc. update:
* [svn-r9991] Purpose:Robert E. McGrath2005-02-111-0/+23
Feature Description: dumper support for nbit Solution: Platforms tested: Misc. update: