summaryrefslogtreecommitdiffstats
path: root/tools/h4toh5main.h
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r2839] MuQun Yang2000-11-081-2/+45
| | | | | | | | | | | | | | | | | | | | | | | | Purpose: check in beta release h4toh5 converter Description: 1. add copy right and other comments to all .h and .c files 2. fix bugs on sds unlimited dimension, hdf5 dimensional scale attribute and vdata translating from h4 to h5. Solution: 2. 1) for sds with unlimited dimension to be converted into extensible hdf5 dataset, on hdf5 side, has to set a default chunk size even though the corresponding hdf4 file is not chunked. 2) in this version, if sds object doesn't have dimensional scale data, we will not show the default hdf4 dimensional name ("fakedim0", etc.) in the new hdf5 dimensional scale name attribute. 3) fix a bug transferring vdata of which the field includes a character array. Make it correctly transfer into the corresponding hdf5 compound data type. Platforms tested: eirene,arabica,baldric,hawkwind,paz,gondolin on new set of hdf4 test files.
* [svn-r2674] MuQun Yang2000-10-121-0/+10
| | | | | | | | | | | | | | | | | Purpose: 1. fix size of dimensional name list so that the size of dimensional name in dumper output will not change because of different versions of hdf library(h4toh5util.h and h4toh5sds.c). 2. fix bzero routine for windows platform(h4toh5util.h,h4toh5util.c,h4toh5anno.c,h4toh5main.c, h4toh5sds.c) Description: 1. change the MAX_DIM_NAME into 276(MAX_NC_NAME +dimension group name) and hopefully we will not expand the size of MAX_NC_NAME(currently 256) for a long time. 2. create a new routine(h4toh5_ZeroMemory) to zero out memory. Use ZeroMemory in windows and bzero at UNIX. Solution: see Description. Platforms tested: LINUX(eirene),WINDOWS 2000, sun 5.6(baldric and arabica),HP-UX11(opus),DEC(gondolin),IRIX 6.5(paz).
* [svn-r2614] MuQun Yang2000-09-281-0/+56
Purpose: add h4toh5 converter source codes under tools directory. Description: [describe the bug, or describe the new feature, etc] Solution: [details about the changes, algorithm, etc...] [Please as detail as you can since your own explanation is better than others guessing it from the code.] Platforms tested: [machines you have tested the changed version. This is absolute important. Test it out on at least two or three different platforms such as Big-endian-32bit (SUN/IRIX), little-endian-32(LINUX) and 64-bit (IRIX64/UNICOS/DEC-ALPHA) would be good.]