summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r5444] Purpose:Quincey Koziol2002-05-201-1/+1
| | | | | | | | | | Code cleanup Description: Clean up warnings on IRIX64 6.5 (modi4) Platforms tested: IRIX64 6.5 (modi4)
* [svn-r5305] Pedro Vicente Nunes2002-05-012-4/+6
| | | | | | | | | | | | | | | | | | Purpose: user reported a bug on h5 to gif tool Description: h5 to gif did not read an HDF5 image correctly Solution: updated the program so that it reads the updated HDF5 image format to the latest specification the debug version of MSVC was giving a failure on the write of the GIF file, regarding the GIF file pointer this write error is eliminated declaring that pointer a global variable there is still an applicattion error on the exit of the program, only on the debug version of MSVC Platforms tested: w2000
* [svn-r5278] Purpose:Albert Cheng2002-04-283-9/+9
| | | | | | | | | | | | | | | | | | | | | Migrate from configure macros of XYZ_ABC to H5_XYZ_ABC Description: configure generates many macros definitions on the fly and were stored in src/H5config.h which is included by H5public.h. But other software that uses hdf5 may also run their own configure. There can be a clash in macro name space. We decided awhile ago to prepend all generated macros with "H5_" to avoid conflicts. The process has started and this commit completes it (at least attempt to). Solution: Many macros symbols (e.g. SIZEOF_xxx and HAVE_xxx were changed to H5_SIZEOF_xxx and H5_HAVE_xxx). Then H5private.h no longer includes H5config.h. This cuts H5config.h away from HDF5 source code. Pending issues: The module of fortran and pablo are to be resolved in a different commit. Platforms tested: eirene (parallel), arabica (solaris 7 --enable-fortran, --enable-cxx)
* [svn-r5219] Purpose:Quincey Koziol2002-04-222-12/+12
| | | | | | | | | | Code cleanup Description: Clean up warnings from gcc 3.1 Platforms tested: FreeBSD 4.5 (sleipnir)
* [svn-r5200] Purpose:Quincey Koziol2002-04-184-7/+7
| | | | | | | | | | Code Cleanup Description: Clean up compiler warnings from the last bunch of checkins Platforms tested: FreeBSD 4.5 (sleipnir)
* [svn-r5160] Purpose:Bill Wendling2002-04-101-7/+5
| | | | | | Regen Description: Updated Dependencies file...
* [svn-r5143] ./hdf5-devel/tools/h5ls/h5ls.cRobb Matzke2002-04-051-33/+1
| | | | | | | | | | | | Minor h5ls bugfix for compound types with array members. (Similar changes shortly for 1.4 branch). 2002-04-04 16:39:09 Robb Matzke <matzke@arborea.spizella.com> * display_cmpd_type: Removed code to display array dimensions from display_cmpd_type() since this was a holdover from the days when hdf5 didn't have an array datatype and was duplicated by display_array_type().
* [svn-r5120] Purpose:Bill Wendling2002-03-2948-0/+0
| | | | | | | | | HDF4 Removal Description: There were some testfiles still left after we removed HDF4 from the HDF5 tree... Platforms tested: Linux
* [svn-r5088] Purpose:Bill Wendling2002-03-2721-17439/+0
| | | | | | | | Code removal Description: Removed the HDF4 source files from the HDF5 tree. The directories will remain. Use the "-P" option when doing a cvs checkout or update to "prune" the empty directories from your personal tree.
* [svn-r5074] Purpose:Bill Wendling2002-03-201-2/+2
| | | | | | | | | Code Motion Description: Removal of HDF4 from the configure/Makefiles. This is a precursor to the actual physical removal of the HDF4 tools from the HDF5 tree. Platforms tested: Arabica, Dangermouse
* [svn-r5042] Purpose:Bill Wendling2002-03-071-1/+2
| | | | | | | | | | | | | | | | | | Bug Fix Description: Some -I paths weren't included in the h5cc script. That would cause the compiler to fail if it was trying to find gass header files or the like. Solution: Added the CPPFLAGS macro to the h5cc.in file so that it'll be there when it's generated. This will also include some -D options which we compiled the library with, like the LFS flags on Linux. Also changed the configure* files so that it will "chmod" the created h5cc file to 755 (executable) since that wasn't happening all the time... Platforms tested: Linux
* [svn-r5023] Purpose:Bill Wendling2002-02-277-7/+163
| | | | | | | | | | | | | | | | | | | Bug Fix Description: There was a problem with having a lot of groups nested together. We could only handle 1024 characters at most, but, in a parallel program especially, it could occur that there were lots and lots of groups and would be more than 1024. Solution: I made the "objname" part of the obj_t structure a pointer instead of a fixed size. Added code to allocate/deallocate the memory we need for it. Had to fix how the "prefix" was being handled in the h5dump program. It was also set to only 1024 characters in length. I made it dynamic. Added a test case...Go me! Platforms tested: Linux, Solaris
* [svn-r5009] Purpose:Bill Wendling2002-02-251-5/+8
| | | | | | | | | | | Oops Description: I added files for testing the group comments dumping feature, but didn't actually add it to the testh5dump.sh script. Solution: Added it. Platforms tested: Linux
* [svn-r5008] Purpose:Bill Wendling2002-02-259-0/+87
| | | | | | | | Test Add Description: Added a test for dumping files with the multi driver. Platforms tested: Linux
* [svn-r5006] Purpose:Bill Wendling2002-02-2517-0/+140
| | | | | | | | Test Addition Description: Added tests to the h5dumper for split and family file drivers. Platforms tested: Linux
* [svn-r4978] Purpose:Quincey Koziol2002-02-172-6/+8
| | | | | | | | Code cleanup Description: Cleanup compiler warnings found by the SGI compiler and gcc 3.0 Platforms tested: FreeBSD 4.5 w/gcc 3.0 (hack) && IRIX64 (modi4)
* [svn-r4926] Purpose:Bill Wendling2002-02-081-1/+2
| | | | | | | | | | | Bug Fix Description: The library path was relying upon the "exec_prefix" variable. However, we weren't including that into the h5cc script. Solution: Added it. Platforms tested: Linux
* [svn-r4898] ./hdf5-devel/tools/h5ls/h5ls.cRobb Matzke2002-02-011-7/+7
| | | | Fixed copyright notice
* [svn-r4892] ./hdf5-devel/tools/h5ls/h5ls.cRobb Matzke2002-01-311-0/+59
| | | | | | 2002-01-31 15:22:24 Robb Matzke <matzke@arborea.spizella.com> *: Displays array data type information instead of saying `4-byte class-10 unknown'.
* [svn-r4783] Bill Wendling2002-01-051-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Purpose: Small Fix Description: Changed how the list of drivers were listed from: { "driver1", "driver2", /* ... */ "drivern", #ifdef FOO "driverm" #endif }; to { "driver1" ,"driver2" /* ... */ ,"drivern" #ifdef FOO ,"driverm" #endif }; since it's a nicer way of doing the same thing without the annoying warning of an extraneous , if FOO isn't defined. Platforms tested: Dangermouse, Modi4, Kelgia
* [svn-r4782] Bill Wendling2002-01-054-2/+116
| | | | | | | | | | | | | Purpose: Feature Add Description: Added support for dumping Group Comments. This involved a modification of the DDL as well. Solution: Steal code from h5ls and put it in the h5dump. The ddl.html file was updated as normal. And a test was created... Platforms tested: Dangermouse, Modi4, Kelgia
* [svn-r4759] Bill Wendling2001-12-301-1/+6
| | | | | | | | | | | | Purpose: Bug fix Description: The "make depend" command wasn't propagating down into the tools/ directories. Solution: Added the "depend:" part to the Makefile in the tools/ subdirectory. Platforms tested: Linux
* [svn-r4757] Purpose:Albert Cheng2001-12-307-25/+0
| | | | | | | | | | | | | | | | | | Removing the DPSS (gridstorage) driver source code. Description: The DPSS (using Grid-Storage) driver is retired. Removed the configure option with-gridstorage from configure.in. Cvs remove the following files ./src/H5FDdpss.c ./src/H5FDdpss.h ./test/dpss_read.c ./test/dpss_write.c Regenerated Dependencies files (some had to be hand-edited since 'make depend' did not cover them.) Removed reference to DPSS Virtual file driver from H5F.c. Platforms tested: modi4 (Parallel; -with-gass=...), eirene, arabica (fortran, cxx).
* [svn-r4747] Purpose:Quincey Koziol2001-12-202-11/+1
| | | | | | | | | | | | | | Bug Fix. Description: The H5Rget_object_type function could not get the object type for dataset region references. Solution: Added a new function, H5Rget_obj_type, to replace H5Rget_object_type. The new function requires the reference type as an additional parameter, in order to allow queries on different reference types to be performed correctly. Platforms tested: FreeBSD 4.4. (sleipnir)
* [svn-r4719] MuQun Yang2001-12-133-9/+4
| | | | | | | | | Purpose: minor code changes for SDS conversion with unlimited dimension case Description: Solution: Platforms tested: eirene
* [svn-r4718] MuQun Yang2001-12-131-0/+4
| | | | | | | | | | | | | | Purpose: parameter file Description: handle parameters in various special cases. Users donot even have to use this file if they don't have those special needs. 1) memory optimization (should always be set to 0 without handling huge SDS array conversion) 2) unlimited dimension with zero current size, users can use this file to define their chunk size. Solution: Platforms tested: RedHat Zoot 6.2
* [svn-r4717] MuQun Yang2001-12-131-20/+47
| | | | | | | | | | | | | | | | | | | | | | | | Purpose: a bug fix a feature added Description: 1.conversion of unlimited dimension data with the current dimensional size 0 2. Use a parameter file to control some special cases: 1) To subdivide the huge array into hyperslabs, a memory buffer size has i to be set. 2) when current dimensional size is 0, a default chunk size can be set. Solution: bug fixed 1. Old approach: the current dimensional size is set to H5S_UNLIMITED, which is a huge number. The default chunk size is set as a *FIXED* default value. 2. New approach: the current dimensional size is set to the current value 0. Users can provide the chunk size through a parameter file. Platforms tested: eirene [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.]
* [svn-r4702] MuQun Yang2001-12-121-4/+21
| | | | | | | | | | Purpose: bug fixed Description: Make HDF4 dataset converted from Vdata extensible. Solution: Platforms tested: RedHat 6.2(Linux)
* [svn-r4701] MuQun Yang2001-12-123-0/+0
| | | | | | | | | | | | Purpose: bug fixed Description: HDF4 Vdata is extensible, when converted, the new HDF4 data set should also be extensible. Solution: Make the HDF4 dataset converted from Vdata unlimited dimensions. These three testing files should be updated accordingly. Platforms tested: Linux, RedHat 6.2
* [svn-r4676] Purpose:Quincey Koziol2001-12-052-0/+12
| | | | | | | | | | | | | | | | Backward Compatibility Fix Description: One of H5P[gs]et_buffer's parameters changed between v1.4 and the development branch. Solution: Added v1.4 compat stuff around H5P[gs]et_buffer implementation and testing to allow v1.4.x users to continue to use their source code without modification. These changes are for everything except the FORTRAN wrappers - I spoke with Elena and she will make the FORTRAN wrapper changes. Platforms tested: FreeBSD 4.4 (hawkwind)
* [svn-r4643] Purpose:Quincey Koziol2001-11-277-34/+50
| | | | | | | | | | | | | | | | | | | | | | Code cleanup Description: Windows is generating hundreds of warnings from some of the practices in the library. Mostly, they are because size_t is 32-bit and hsize_t is 64-bit on Windows and we were carelessly casting the larger values down to the smaller ones without checking for overflow. Also, some other small code cleanups,etc. Solution: Re-worked some algorithms to eliminate the casts and also added more overflow checking for assignments and function parameters which needed casts. Kent did most of the work, I just went over his changes and fit them into the the library code a bit better. Platforms tested: FreeBSD 4.4 (hawkwind)
* [svn-r4612] MuQun Yang2001-11-194-21/+240
| | | | | | | | | | | | | | | | | Purpose: A new feature Description: While testing h4toh5 utility with real NASA files, we find an example that the data array(one SDS) is so big that it exceeds the physical memory of some machine(>128 MB) and the conversion failed. Before the smart hyperslab operation is out, I am dividing the whole SDS into smaller hyperslabs with each hyperslab propotational to the original SDS array dimensions. For example, a three dimension array with 1000*1000*1000 elements, I can divide them into eight 500*500*500 pieces. I can read and write each piece and remember their starting and ending points. In this way, the memory allocation failure can be avoided; however, it may not be the efficient way. I've tested this feature using SDS without chunking. It works fine. However, when testing SDS with chunking, it is extremely slow. This happens to be a bug in HDF5 library now. Quincey may fix this later and give me a more efficient way to handle the problem. Currently all my testing files are with UNLIMITED dimensions, so in HDF5 the chunking feature will be required. SO by default, this feature will not be turned on. Solution: see the above Platforms tested: linux 2.2.18
* [svn-r4591] Purpose:Quincey Koziol2001-11-048-40/+37
| | | | | | | | Code cleanup Description: Fix a bunch of warnings Platforms tested: Linux 2.2 (eirene)
* [svn-r4517] Raymond Lu2001-10-033-11/+12
| | | | | | | | Purpose: Changed to the new generic property list for dataset creation property list. Platforms tested: Arabica, modi4 and Hawkwind
* [svn-r4482] Purpose:Quincey Koziol2001-09-261-2/+2
| | | | | | | | | | | | | | | | | | | | | | Kludge Description: Since we're only about halfway through converting the internal use of property lists from the "old way" to the generic property lists, we turned off snapshots to avoid exposing lots of API changes to users, until the APIs settled down. Getting the snapshots rolling again seems to have become a priority, so some changes are going to have to be made now that were going to be postponed until we were completely finished with the conversion. This requires that the old API functions be able to deal with both the old and new property lists smoothly. Solution: Kludge together the property list code so that they can transparently handle dealing with both the old and new property lists Platforms tested: FreeBSD 4.4 (hawkwind)
* [svn-r4473] Purpose:Quincey Koziol2001-09-256-216/+227
| | | | | | | | | | | | | | | | | | | | | Code cleanup for better compatibility with C++ compilers Description: C++ compilers are choking on our C code, for various reasons: we used our UNUSED macro incorrectly when referring to pointer types we used various C++ keywords as variables, etc. we incremented enum's with the ++ operator. Solution: Changed variables, etc.to avoid C++ keywords (new, class, typename, typeid, template) Fixed usage of UNUSED macro from this: char UNUSED *c to this: char * UNUSED c Switched the enums from x++ to x=x+1 Platforms tested: FreeBSD 4.4 (hawkwind)
* [svn-r4456] Bill Wendling2001-09-181-54/+53
| | | | | | | | | | | | | Purpose: Bug Fix Description: Some so-called "operating systems" (*cough*Windows*cough*) can't handle large string sizes. Solution: Replace the Usage string with individual strings which all call fprintf() themselves. Platforms tested: Linux
* [svn-r4455] Bill Wendling2001-09-182-9/+9
| | | | | | | | | Purpose: Warning Removal Description: Remove some spurious warnings from the compilation. Platforms tested: Linux
* [svn-r4402] Bill Wendling2001-08-211-3/+3
| | | | | | | | | | | | Purpose: Bug Fix Description: Object IDs command-line options weren't being picked up. Solution: The wrong flag was being checked for. Changed the flag from "v" to "i", which is what the documentation says. Platforms tested: Linux
* [svn-r4376] MuQun Yang2001-08-171-0/+0
| | | | | | | | | Purpose: add another raster image 24-bit test files Description: Solution: Platforms tested: sol 2.7 and RedHat Zoot 6.2
* [svn-r4375] MuQun Yang2001-08-175-0/+0
| | | | | | | | | Purpose: update the expected HDF5 files to follow the interlace mode convention in HDF5 image spec. Description: Solution: Platforms tested:
* [svn-r4374] MuQun Yang2001-08-171-0/+0
| | | | | | | | | | | | | | Purpose: add another test file Description: Solution: Platforms tested: eirene, arabica [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.]
* [svn-r4373] MuQun Yang2001-08-171-0/+0
| | | | | | | | | | | | | Purpose: Add another test file Description: Solution: Platforms tested: eirene, arabica [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.]
* [svn-r4372] MuQun Yang2001-08-171-0/+1
| | | | | | | Purpose: add another test case. Description: Solution:
* [svn-r4371] MuQun Yang2001-08-171-3/+3
| | | | | | | | | | | Purpose: a bug fix Description: change PIXEL_INTERLACE to INTERLACE_PIXEL and other interlace mode description to fit for the image specification. Solution: Platforms tested: eirene, sol2.7
* [svn-r4370] MuQun Yang2001-08-171-6/+18
| | | | | | | | | | | | | | | Purpose: 1. fix a bug 2. turn off a feature Description: 1. change the output of GRgetiminfo from NULL to &interlace_mode. 2. turn off the feature to change line-interleaved feature into pixel-interleaved feature since inconsistent behaviour is found in GR interface. Solution: see above Platforms tested: eirene, arabica
* [svn-r4369] MuQun Yang2001-08-171-7/+151
| | | | | | | | | | | | | | | Purpose: add a real raster-24 bit testing for interlace mode. Description: 1. GR interfaces will never create an HDF4 file with interlace mode other than pixel interleaved. DF24 interfaces can create HDF4 file with different interleaved. There are inconsistent behaviors between GRreqimageil and GRreadimage, data read into the memory will not behave properly if a new interlace mode is asked. 2. Currently HDF5 image spec. supports pixel interleaved and plane interleaved. We make a real image file to test whether the converter is doing the right thing. Solution: We use DF24 bit APIs to generate a real image file that can be tested by H5view. Platforms tested: linux and sol2.7
* [svn-r4355] Purpose:Quincey Koziol2001-08-145-22/+22
| | | | | | | | | | | | | | | | | | | | | | Code cleanup (sorta) Description: When the first versions of the HDF5 library were designed, I remembered vividly the difficulties of porting code from a 32-bit platform to a 16-bit platform and asked that people use intn & uintn instead of int & unsigned int, respectively. However, in hindsight, this was overkill and unnecessary since we weren't going to be porting the HDF5 library to 16-bit architectures. Currently, the extra uintn & intn typedefs are causing problems for users who'd like to include both the HDF5 and HDF4 header files in one source module (like Kent's h4toh5 library). Solution: Changed the uintn & intn's to unsigned and int's respectively. Platforms tested: FreeBSD 4.4 (hawkwind)
* [svn-r4345] Purpose:Albert Cheng2001-08-144-8/+8
| | | | | | | | | | | | | | | | | | | | | Improvement Description: The stdout and stderr were both redirected to an output file. This works fine in tradition sequential Unix machines. But in some parallel systems (like mpi-jobs in IBM SP), the stderr is merged with stdout alright but not in the exact order as expected. This is not deterministic in parallel jobs. So, the test output are all there but the ordering maynot be as expected. Solution: Redirect stderr to separated file and append it to the stdout file after test-command is executed. Then compare it with the expected output. This eliminate the assumption that stdout and stderr must merged in "chronical orders". The .ddl file are updated by moving all stderr text to the end of the file. Platforms tested: eirene.
* [svn-r4342] Purpose:Albert Cheng2001-08-141-3/+4
| | | | | | | | | | | | | | | | | | Improvement Description: The stdout and stderr were both redirected to an output file. This works fine in tradition sequential Unix machines. But in some parallel systems (like mpi-jobs in IBM SP), the stderr is merged with stdout alright but not in the exact order as expected. This is not deterministic in parallel jobs. So, the test output are all there but the ordering maynot be as expected. Solution: Redirect stderr to separated file and append it to the stdout file after test-command is executed. Then compare it with the expected output. This eliminate the assumption that stdout and stderr must merged in "chronical orders". Platforms tested: tested in v1.4. Folded it into v1.5.
generated by cgit v0.12 at 2024-11-03 13:30:12 (GMT)