.gitattributes

+* text=auto !eol
+/AUTHORS -text
+/COPYING -text
+/ChangeLog -text
+/GNUmakefile.orig -text
+/INSTALL -text
+/Makefile.am -text
+/Makefile.orig -text
+/NEWS -text
+/README -text
+/autogen.sh -text
+/config.guess -text
+/config.sub -text
+/configure.ac -text
+/depcomp -text
+doc/Doxyfile -text
+doc/H5X_File_Format.txt -text
+doc/Makefile.am -text
+doc/doxyfooter -text
+/install-sh -text
+/license.txt -text
+/missing -text
+/rules.make -text
+src/H5Block.c -text
+src/H5Block.h -text
+src/H5BlockErrors.h -text
+src/H5BlockF.c -text
+src/H5BlockF90.inc -text
+src/H5BlockPrivate.h -text
+src/H5BlockTypes.h -text
+src/H5Part.c -text
+src/H5Part.h -text
+src/H5PartErrors.h -text
+src/H5PartF.c -text
+src/H5PartF90.inc -text
+src/H5PartPrivate.h -text
+src/H5PartTypes.h -text
+src/Makefile.am -text
+src/TestUnderscore.f -text
+src/TestUnderscoreC.c -text
+test/Bench.c -text
+test/BlockTestSpecs.txt -text
+test/H5BlockDissolveGhosts.c -text
+test/H5BlockParTestScalarField.c -text
+test/H5BlockParTestScalarField.pbs -text
+test/H5BlockParTestScalarFieldF.f90 -text
+test/H5BlockTestAttributes.c -text
+test/H5BlockTestAttributesF.f90 -text
+test/H5ParallelTest.cc -text
+test/H5PartAndreasTest.cc -text
+test/H5PartTest.cc -text
+test/H5PartTestParallel.cc -text
+test/H5test.cc -text
+test/H5testF.f -text
+test/H5testFpar.f90 -text
+test/Makefile.am -text
+tools/Makefile.am -text
+tools/README -text
+tools/h5ToVtk.cc -text
+tools/h5pAttrib.cc -text
+tools/h5pToGNUplot.cc -text
+tools/homdynToH5p.cc -text
+visit_plugins/databases/H5Part/.depend -text
+visit_plugins/databases/H5Part/Makefile -text
+visit_plugins/databases/H5Part/README.txt -text
+visit_plugins/databases/H5Part/avth5partFileFormat.C -text
+visit_plugins/databases/H5Part/avth5partFileFormat.h -text
+visit_plugins/databases/H5Part/h5part.xml -text
+visit_plugins/databases/H5Part/h5partCommonPluginInfo.C -text
+visit_plugins/databases/H5Part/h5partEnginePluginInfo.C -text
+visit_plugins/databases/H5Part/h5partMDServerPluginInfo.C -text
+visit_plugins/databases/H5Part/h5partPluginInfo.C -text
+visit_plugins/databases/H5Part/h5partPluginInfo.h -text
+visit_plugins/operators/BinnerFilter/.depend -text
+visit_plugins/operators/BinnerFilter/Binner.xml -text
+visit_plugins/operators/BinnerFilter/BinnerCommonPluginInfo.C -text
+visit_plugins/operators/BinnerFilter/BinnerEnginePluginInfo.C -text
+visit_plugins/operators/BinnerFilter/BinnerFilter.C -text
+visit_plugins/operators/BinnerFilter/BinnerFilter.h -text
+visit_plugins/operators/BinnerFilter/BinnerFilter.java -text
+visit_plugins/operators/BinnerFilter/BinnerGUIPluginInfo.C -text
+visit_plugins/operators/BinnerFilter/BinnerMakefile -text
+visit_plugins/operators/BinnerFilter/BinnerPluginInfo.C -text
+visit_plugins/operators/BinnerFilter/BinnerPluginInfo.h -text
+visit_plugins/operators/BinnerFilter/BinnerScriptingPluginInfo.C -text
+visit_plugins/operators/BinnerFilter/BinnerViewerPluginInfo.C -text
+visit_plugins/operators/BinnerFilter/Binnerreplace.txt -text
+visit_plugins/operators/BinnerFilter/Makefile -text
+visit_plugins/operators/BinnerFilter/PyBinner.C -text
+visit_plugins/operators/BinnerFilter/PyBinner.h -text
+visit_plugins/operators/BinnerFilter/QvisBinnerWindow.C -text
+visit_plugins/operators/BinnerFilter/QvisBinnerWindow.h -text
+visit_plugins/operators/BinnerFilter/avtBinnerFilter.C -text
+visit_plugins/operators/BinnerFilter/avtBinnerFilter.h -text
+visit_plugins/operators/BinnerFilter/icon.xpm -text
+visit_plugins/operators/RandomSample/.depend -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleAttributes.C -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleAttributes.h -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleAttributes.java -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleCommonPluginInfo.C -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleEnginePluginInfo.C -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleGUIPluginInfo.C -text
+visit_plugins/operators/RandomSample/H5PartRandomSamplePluginInfo.C -text
+visit_plugins/operators/RandomSample/H5PartRandomSamplePluginInfo.h -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleScriptingPluginInfo.C -text
+visit_plugins/operators/RandomSample/H5PartRandomSampleViewerPluginInfo.C -text
+visit_plugins/operators/RandomSample/Makefile -text
+visit_plugins/operators/RandomSample/PyH5PartRandomSampleAttributes.C -text
+visit_plugins/operators/RandomSample/PyH5PartRandomSampleAttributes.h -text
+visit_plugins/operators/RandomSample/QvisH5PartRandomSampleWindow.C -text
+visit_plugins/operators/RandomSample/QvisH5PartRandomSampleWindow.h -text
+visit_plugins/operators/RandomSample/RandomSample.xml -text
+visit_plugins/operators/RandomSample/avtH5PartRandomSampleFilter.C -text
+visit_plugins/operators/RandomSample/avtH5PartRandomSampleFilter.h -text
+visit_plugins/operators/RandomSample/icon.xpm -text

AUTHORS

+
+Andreas Adelmann (PSI)
+Achim Gsell (PSI)
+Benedikt Oswald (PSI)
+
+Wes Bethel (NERSC/LBNL)
+John Shalf (NERSC/LBNL)
+Cristina Siegerist (NERSC/LBNL)
+Mark Howison (NERSC/LBNL)
+
+Please use h5part@lists.psi.ch for communicaion.

COPYING

+*** Copyright Notice ***
+
+H5Part  Copyright (c) 2006-2009, The Regents of the University of California,
+through Lawrence Berkeley National Laboratory (subject to receipt of any
+required approvals from the U.S. Dept. of Energy) and the Paul Scherrer
+Institut (Switzerland).  All rights reserved.
+
+If you have questions about your rights to use or distribute this
+software, please contact Berkeley Lab's Technology Transfer Department
+at  TTD@lbl.gov referring to "H5Part (LBNL Ref CR-2255)"
+
+NOTICE.  This software was developed under partial funding from the U.S.
+Department of Energy.  As such, the U.S. Government has been granted for
+itself and others acting on its behalf a paid-up, nonexclusive,
+irrevocable, worldwide license in the Software to reproduce, prepare
+derivative works, and perform publicly and display publicly.  Beginning
+five (5) years after the date permission to assert copyright is obtained
+from the U.S. Department of Energy, and subject to any subsequent five
+(5) year renewals, the U.S. Government is granted for itself and others
+acting on its behalf a paid-up, nonexclusive, irrevocable, worldwide
+license in the Software to reproduce, prepare derivative works,
+distribute copies to the public, perform publicly and display publicly,
+and to permit others to do so.
+
+
+*** License agreement ***
+
+H5Part  Copyright (c) 2006-2009, The Regents of the University of California,
+through Lawrence Berkeley National Laboratory (subject to receipt of any
+required approvals from the U.S. Dept. of Energy) and the Paul Scherrer
+Institut (Switzerland).  All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+(1) Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+
+(2) Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+
+(3) Neither the name of the University of California, Lawrence Berkeley
+National Laboratory, U.S. Dept. of Energy, Paul Scherrer Institut
+(Switzerland) nor the names of its contributors may be used to endorse
+or promote products derived from this software without specific prior
+written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
+IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
+OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+You are under no obligation whatsoever to provide any bug fixes,
+patches, or upgrades to the features, functionality or performance of
+the source code ("Enhancements") to anyone; however, if you choose to
+make your Enhancements available either publicly, or directly to
+Lawrence Berkeley National Laboratory, without imposing a separate
+written license agreement for such Enhancements, then you hereby grant
+the following license: a  non-exclusive, royalty-free perpetual license
+to install, use, modify, prepare derivative works, incorporate into
+other computer software, distribute, and sublicense such enhancements or
+derivative works thereof, in binary and source code form.
+

ChangeLog

+2008-12-19  Mark Howison  <mhowison@lbl.gov>
+
+	* Added support for HDF 1.8.1.
+
+	* Added float32 and int64 versions of the H5Block scalar field
+	read/write functions, using a new naming convention: 
+        
+        H5Block3dWriteScalarFieldFloat64() (was H5Block3dWriteScalarField())
+        H5Block3dWriteScalarFieldFloat32() (new)
+        H5Block3dWriteScalarFieldInt64()   (new)
+
+	* Modified _write_data() in H5Block to write arbitrary data types.
+
+	* Fixed a bug in the configure script which was preventing
+	compilation of the FORTRAN library on Cray XT4 architectures.
+	
+	* Added the "--with-mpiposix" option to the configure script to enable
+	the MPI-POSIX VFD in the HDF5 layer.
+
+2008-11-20  Andreas Adelmann  <andreas.adelmann@psi.ch>
+
+	* Fixed a bug in ./test/H5BlockTestAttributes.c
+
+	

GNUmakefile.orig

+UNAME := $(shell uname | perl -pe 's/(sn\d\d\d\d|jsimpson)/UNICOS\/mk/')
+# for host specific options
+HOST := $(shell hostname)
+
+# for processor-specific options
+ifeq ($(UNAME), Linux)
+PROC := $(shell uname -p)
+endif
+
+CXX = c++
+CC = cc
+H5HOME = /usr/local/hdf5
+CFLAGS = -g -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+
+# MacOS-X Serial
+ifeq ($(UNAME), Darwin)
+ifeq ($(PARALLEL), yes)
+CXX = g++
+CC = mpicc
+H5HOME = /usr/local
+CFLAGS = -O -g -I$(H5HOME)/include -DPARALLEL_IO
+LDFLAGS = -L$(H5HOME)/lib -lmpich -lpmpich -lhdf5 -lz -lm
+else
+CXX = c++
+CC = cc
+F90 = xlf
+H5HOME = /usr/local
+CFLAGS = -O -g -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+endif
+endif
+
+# SGI MIPS/Irix
+ifeq ($(UNAME), IRIX64)
+CXX = CC
+CC = cc
+F90 = f90
+ifeq ($(PARALLEL), yes)
+H5HOME = $(HDF5_DIR)
+CFLAGS = -64 -O3 -I$(H5HOME)/include -DPARALLEL_IO
+LDFLAGS = -64 -O3 -L$(H5HOME)/lib -lhdf5 -lz -lmpi -lm
+else
+H5HOME = /usr/local
+CFLAGS = -O3 -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+endif
+endif
+
+# AIX/SP-2 Parallel/serial : Seaborg
+ifeq ($(UNAME), AIX)
+ifeq ($(PARALLEL), yes) # parallel
+CXX = mpCC_r
+CC = mpxlc_r
+# H5HOME = /usr/common/usg/hdf5_64/1.4.5-post2/parallel
+H5HOME = /usr/common/usg/hdf5_64/1.6.1/parallel
+# /usr/common/usg/hdf5/1.4.4/parallel
+H4HOME = /usr/common/usg/hdf/default
+OPT = -qarch=auto -qtune=auto-qcache=auto -O3 -qhot
+CFLAGS = -q64 -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -L$(H4HOME)/lib -lz -lsz -lm
+else # serial
+CXX = xlC
+CC = xlc
+H5HOME = /usr/common/usg/hdf5/1.4.4/serial
+H4HOME = /usr/common/usg/hdf/default
+OPT = -qarch=auto -qtune=auto-qcache=auto -O3 -qhot
+CFLAGS = -g -bmaxdata:800000000  -bmaxstack:256000000 -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -L$(H4HOME)/lib -lz -lm
+endif
+endif
+
+# Linux
+ifeq ($(UNAME), Linux)
+# if this machine is NERSC/Davinci Altix system
+ifeq ($(PROC), ia64)
+CC = icc 
+CXX = icc
+
+ifeq ($(PARALLEL), yes)
+# IA64 Linux Parallel
+ifeq ($(HOST), davinci)
+H5HOME = $(HDF5_PAR)
+MPILIB = -lmpi
+else
+H5HOME = /usr/local
+HDF5_PAR_LIB = -L$(H5HOME)/lib -lhdf5 -lz -lm
+HDF5_PAR_INCLUDE = -I$(H5HOME)/include
+MPIHOME = /usr/local
+MPILIB = -lmpich
+endif # HOST
+CFLAGS = -O3 -DPARALLEL_IO -DH5_HAVE_PARALLEL $(HDF5_PAR_INCLUDE) 
+LDFLAGS = $(HDF5_PAR_LIB) $(MPILIB)
+else # IA64 Linux Serial
+CFLAGS = -O3 $(HDF5_INCLUDE)
+LDFLAGS = $(HDF5_LIB) -lm
+endif # PARALLEL
+
+# else this is standard IA32 linux
+else
+ifeq ($(PARALLEL), yes)
+# Linux Parallel
+CC = gcc
+CXX = g++
+H5HOME = /usr/local
+MPIHOME = /usr/local
+CFLAGS = -O -g -DPARALLEL_IO -DH5_HAVE_PARALLEL -I$(H5HOME)/include 
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lmpich -lrt -lz -lm
+else # Linux Serial
+CXX = g++
+CC = gcc
+CFLAGS = -O -g -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+endif # !PARALLEL
+endif # PROC!ia64
+
+endif # !Linux
+
+ifeq ($(PARALLEL), yes) #parallel
+ifdef F90
+all: H5PartTest H5PartTest.o H5Part.o H5PartTestParallel H5PartAndreasTest H5PartF.o
+else
+all: H5PartTest H5PartTest.o H5Part.o H5PartTestParallel H5PartAndreasTest
+endif
+else
+ifdef F90
+all: H5PartTest H5PartTest.o H5Part.o H5PartF.o
+else
+all: H5PartTest H5PartTest.o H5Part.o
+endif
+endif
+
+include rules.make

Makefile.am

+# Trial by Antino Kim
+# Top level Makefile.am
+
+SUBDIRS = \
+	doc \
+	src \
+	test \
+	tools
+
+MAINTAINERCLEANFILES = \
+	config.h \
+	config.log \
+	config.status \
+	stamp-h.in \
+	stamp-h1

Makefile.orig

+
+# This is a very rudimentary multiarchitecture makefile
+# You need to uncomment the default block of make variables you need
+# Some key things to watch for are the following defines
+#	-DREGRESSIONTEST : enables a main(){} inside of
+#		the H5Part.cc file that does simple regression testing.
+#	-DPARALLEL_IO : If you want to use parallel HDF5, you have to 
+#		enable this.  Otherwise, you get only the serial 
+#		implementation of the library.  
+
+# MacOS-X Serial
+#CXX = c++
+#CC = cc
+#F90 = xlf
+#H5HOME = /usr/local
+#CFLAGS = -O -g -I$(H5HOME)/include
+#LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+
+# AIX/SP-2 Parallel : Seaborg
+#CXX = mpCC_r
+#CC = mpcc_r
+#F90 = mpxlf
+#H5HOME = /usr/common/usg/hdf5/1.4.4/parallel
+#H4HOME = /usr/common/usg/hdf/default
+#OPT = -qarch=auto -qtune=auto-qcache=auto -O3 -qhot
+#CFLAGS = -g -bmaxdata:800000000  -bmaxstack:256000000 -I$(H5HOME)/include
+#LDFLAGS = -L$(H5HOME)/lib -lhdf5 -L$(H4HOME)/lib -lz -lm
+
+# Linux Serial
+#CXX = g++
+#CC = gcc
+#F90 = g77  # or could be pgif90
+#CFLAGS = -O -g -I$(H5HOME)/include
+#LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+
+# Linux Jacquard
+CC = mpicc
+CXX = mpicxx
+F90 = mpif90
+H5HOME = /usr/common/usg/hdf5/1.6.3/parallel
+CFLAGS = -O2 -DPARALLEL_IO -DH5_HAVE_PARALLEL -I$(H5HOME)/include
+LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lz -lm
+
+# Linux Parallel
+#CC = gcc
+#CXX = g++
+#F90 = g77
+#H5HOME = /usr/local
+# /usr/common/usg/hdf5/1.6.3/parallel
+#MPIHOME = /usr/local
+#CFLAGS = -O -g -DPARALLEL_IO -DH5_HAVE_PARALLEL -I$(H5HOME)/include 
+#LDFLAGS = -L$(H5HOME)/lib -lhdf5 -lmpich -lrt -lz -lm
+
+all: H5PartTest H5PartTest.o H5Part.o
+parallel: H5PartTest H5PartTest.o H5Part.o H5PartTestParallel H5PartAndreasTest # parallel regression tests
+fortran: H5PartF.o # fortran bindings
+
+include rules.make
+

NEWS

+VERSION 1.4.1
+*************
+
+* Added support for HDF 1.8.1.
+
+* Added float32 and int64 versions of the H5Block scalar field
+read/write functions, using a new naming convention:
+        
+        H5Block3dWriteScalarFieldFloat64() (was H5Block3dWriteScalarField())
+        H5Block3dWriteScalarFieldFloat32() (new)
+        H5Block3dWriteScalarFieldInt64()   (new)
+
+The old functions still exist, but may be removed in the future.
+
+
+VERSION 1.4.0
+*************
+
+Error Handling
+--------------
+ Now all functions, in which an error could occure, are returning a
+value. This value is either a 64bit integer or a pointer.
+
+ A negative 64bit integer as result indicates an error. Values >= 0
+indicates successfull execution.   This is similiar to the convention
+used in UNIX system calls, but we do not return -1 but the error
+number (which is always negative).
+
+ For functions returning a pointer the NULL-pointer is used to indicate
+an error. You can call the function H5PartGetErrno() to get the error
+number.  For the time being there is no strerror(3) or perror(3)
+equivalent. 
+
+
+API Changes
+-----------
+ There are several changes in the API of H5Part. The biggest change is
+a side-effect of the implementation of strict error handling.  The
+impact to the existing C/C++ code is very small.  But now you *can*
+and *should* implement some kind of error handling.  The simplest
+error handling is to set an error handler which aborts the program as
+soon as an error occured.
+
+ The next "biggest" change is the use of H5Part types instead of "long
+long" and "double". The replacement of "long long" is "h5part_int64_t"
+and for "double" "h5part_float64_t". This change has now effect in
+Fortran.  
+
+ In some functions the argument type changed from "int" to
+"h5part_int64_t". Since on most systems "int" is a 32bit integer,
+calls to these functions must be adapted to the new API. In C/C++ the
+compiler will complain about it. But in Fortran you will *not* get an
+error message.So, you must check your Fortran code carefully.
+
+ Changes in detail (not listed are functions where only the return
+type changed from any to "h5part_int64_t"):
+
+	New API					Changes to old API
+
+	h5part_int64_t				void
+	H5PartSetNumParticles (
+		H5PartFile *f,
+		h5part_int64_t nparticles	long long
+		);
+
+	h5part_int64_t				int
+	H5PartWriteDataFloat64 (
+		H5PartFile *f,
+		char *name, 
+		h5part_float64_t *dta		double
+		);
+
+	h5part_int64_t				int
+	H5PartWriteDataInt64 (
+		H5PartFile *f,
+		char *name,
+		h5part_int64_t *dta		long long
+		);
+
+	h5part_int64_t				void
+	H5PartSetStep (
+		H5PartFile *f,
+		h5part_int64_t step		int
+		);
+
+	h5part_int64_t				void
+	H5PartSetView (
+		H5PartFile *f,
+		h5part_int64_t start,		long long
+		h5part_int64_t end		long long
+		);
+
+	h5part_int64_t				int
+	H5PartGetView (
+		H5PartFile *f,
+		h5part_int64_t *start,		long long
+		h5part_int64_t *end		long long
+		);
+
+	h5part_int64_t				int
+	H5PartReadDataFloat64 (
+		H5PartFile *f,
+		char *name,
+		h5part_float64_t *dta		double
+		);
+
+	h5part_int64_t				int
+	H5PartReadDataInt64 (
+		H5PartFile *f,
+		char *name,
+		h5part_int64_t *dta		long long
+		);
+    
+	h5part_int64_t				void
+	H5PartReadParticleStep (		
+		H5PartFile *f,
+		h5part_int64_t step,		int
+		h5part_float64_t *x,		double
+		h5part_float64_t *y,		double
+		h5part_float64_t *z,		double
+		h5part_float64_t *px,		double
+		h5part_float64_t *py,		double
+		h5part_float64_t *pz,		double
+		h5part_int64_t *id		long long
+		);
+
+New functions:
+
+	h5part_int64_t
+	H5PartSetVerbosityLevel (
+		unsigned int
+		);
+
+	h5part_int64_t
+	H5PartSetErrorHandler ( 
+		h5part_error_handler handler
+		);
+
+	h5part_int64_t
+	H5PartGetErrno (
+		void
+		);
+
+	h5part_int64_t
+	H5PartDefaultErrorHandler (
+		const char *funcname,
+		const h5part_int64_t eno,
+		const char *fmt,
+		...
+		);
+
+	h5part_int64_t
+	H5PartAbortErrorHandler (
+		const char *funcname,
+		const h5part_int64_t eno,
+		const char *fmt,
+		...
+		);
+
+Removed functions:
+
+	int
+	H5PartFileIsValid (
+		H5PartFile *f
+		);

README

+For more information on using the H5Part API, see the H5Part website:
+
+        http://www-vis.lbl.gov/Research/AcceleratorSAPP/
+
+
+Motivation
+----------
+
+Particle based simulations of accelerator beam-lines, especially in six
+dimensional phase space, generate vast amounts of data. Even though a subset
+of statistical information regarding phase space or analysis needs to be
+preserved, reading and writing such enormous restart files on massively
+parallel supercomputing systems remains challenging.
+
+H5Part is a very simple data storage schema and provides an API that
+simplifies the reading/writing of the data to the HDF5 file format. An
+important foundation for a stable visualization and data analysis environment
+is a stable and portable file storage format and its associated APIs. The
+presence of a "common file storage format," including associated APIs, will
+help foster a fundamental level of interoperability across the project's
+software infrastructure. It will also help ensure that key data analysis
+capabilities are present during the earliest phases of the software development
+effort.
+
+H5Part is built on top of the HDF5 (Hierarchical Data Format) library. HDF5
+offers a self-describing machine-independent binary file format that supports
+scalable parallel I/O performance for MPI codes on a variety of supercomputing
+systems, and works equally well on laptop computers. The API is available for
+C, C++, and Fortran codes. The H5Part file format and APIs enable disparate
+research groups with different simulation implementations to transparently
+share datasets and data analysis tools. For instance, the common file format
+will enable groups that depend on completely different simulation
+implementations to share data analysis tools.
+
+
+File Organization and API
+-------------------------
+
+The proposed file storage format uses HDF5 for the lowlevel file storage and a
+simple API to provide a high-level interface to that file format. A programmer
+can either use the H5Part API to access the data files or write directly to the
+file format using some simple conventions for organizing and naming the objects
+stored in the file.
+
+In order to store Particle Data in the HDF5 file format, we have formalized the
+hierarchical arrangement of the datasets and naming conventions for the groups
+and associated datasets. The sample H5Part API formally encodes these
+conventions in order to provide a simple and uniform way to access these files
+from C, C++, and Fortran codes. The API makes it easier to write very portable
+data adaptors for visualization tools in order to expand the number of tools
+available to access the data. Even so, anyone can use the HDF5 h5ls utility to
+examine the organization of the H5Part files and even write their own
+HDF5-based interface for reading and writing the file format. The standards
+offered by the sample API are completely independent of the standard for
+organizing data within the file.The file format supports the storage of
+multiple timesteps of datasets that contain multiple fields. 
+

autogen.sh

+#!/bin/sh
+# Run this to generate all the initial makefiles, etc.
+
+echo "+ making misc files ..."
+touch NEWS README AUTHORS ChangeLog
+echo
+echo
+echo
+echo "+ running aclocal ..."
+aclocal $ACLOCAL_FLAGS || {
+  echo
+  echo "aclocal failed - check that all needed development files are present on system"
+  exit 1
+}
+echo
+echo
+echo
+echo
+echo "+ running autoheader ... "
+autoheader || {
+  echo
+  echo "autoheader failed"
+  exit 1
+}
+echo
+echo
+echo
+echo "+ running autoconf ... "
+autoconf || {
+  echo
+  echo "autoconf failed"
+  exit 1
+}
+echo
+echo
+echo
+echo "+ running automake ... "
+automake -a -c --foreign || {
+  echo
+  echo "automake failed"
+  exit 1
+}
+echo
+echo
+echo
+

doc/H5X_File_Format.txt

+Proposal for a more general file format used by H5Part/H5Block
+
+                                                 Authors: Achim Gsell
+                                                 Status:  Draft
+
+1. Introduction
+
+H5X is the file format used by H5Part and H5Block.  H5X is designed on
+top of HDF5: A H5X file is a very special HDF5 file.
+
+	+--------------------+
+	|   Application      |
+	+--------------------+
+	| H5Part/H5Block API |
+	+--------------------+
+	|      H5X API       |
+	+--------------------+
+	|     HDF5 API       |
+	+--------------------+
+	|  Filesystem of OS  |
+	+--------------------+
+
+
+2. H5X file format specification
+
+2.1 The root group
+
+2.1.1 File attributes
+
+Attributes of the HDF5 root group are called "file attributes". There
+are no restrictions on file attribute names.  Names with "__" as prefix and
+postfix are intended for internal use. Supported values for file attributes
+are scalars and arrays of 64bit integer and 64bit floating point number as
+well as string values. Arrays of strings are not supported.
+
+2.1.1.1 Predefined file attributes
+
+__stepname__ (optional)
+	See below.
+
+__stepnumwidth__ (optional)
+	See below.
+
+2.1.2 Members of the root group
+
+Members of the root group are special formated HDF5 groups called
+"step groups".  The name of a step group is "<name>#<number>". 
+Whereby <name> is either defined by the optional file attribute
+__stepname__ or set to "Step" by default. <number> is an 
+unsigned integer less than 2^63. 
+
+/
++- Step#0
++- Step#1
+...
++- Step#n
++- StepProperties [NEW]
++- Mesh [NEW]
+
+The optional file attribute __stepnumwidth__ defines the minimum width
+of <number> in the name of the step group. The number is padded with
+'0'. The minimum width defaults to zero, so that no paddings occurs. 
+Example: With __stepnumwidth__ := 5 the name of the step group with
+number 42 is "Step#00042", with __stepnumwidth__ := 0 the name is
+"Step#42". 
+
+Step groups may be unsorted in the HDF5 file und needn't be number
+consecutively. 
+
+2.1.3 Other members of the root group
+
+Other sub-groups of the root group are allowed, but the group names are restricted
+to names not matching "Step#.*".
+
+2.2    Format of a step group
+
+2.2.1  Step attributes
+
+Step attributes are HDF5 attributes asigned to a step group.  There
+are no restrictions on step attribute names. As with file attributes names
+enclosed in "__" are intended for internal use. Supported values are the same
+as for file attributes:
+	* 64bit integer value
+	* arrays of 64bit integer values
+	* 64bit floating point number
+	* array of 64bit floating point number
+	* strings
+Note that array of strings are not supported! 
+
+2.2.2  Predefined step attributes
+
+No predefined step attributes exists.
+
+
+2.2.3  Members of a step group
+
+Members of a step group are HDF5 datasets and optional one HDF5 group
+with the name "Block". HDF5 datasets in a step group are called "step
+datasets". The optional block group is called "block data". 
+
+Mesh?!
+
+2.2.4  Step datasets
+
+Step datasets are arrays of rank 1.  The dataset size must be the same
+for all datasets inside a step.  The size of the dataset may vary
+from step to step.  Array values are 64bit integer or 64bit floating
+point numbers. No limitations (other than given by HDF5) are given on
+step dataset names.
+
+
+2.2.5  Block Data
+
+The block data group is a container for an arbitrary number of field
+data. A field is a data structure to store arrays of rank m with
+n-dimensional vector values. Fields are represented within HDF5
+groups. The HDF5 group name is the unique identifier for a field in
+the current step.
+
+2.2.5.1 m-rank fields with n-dimensional-vector values
+
+Values are stored per dimension in separate datasets. Thus we have n
+datasets for a field with n-dimensional vector values.  Each dataset
+corresponse to one dimension. The datasets are numbered from '0' to
+'n-1'. Arrays are stored in column major order (Fortran indexing
+scheme).
+
+/				# HDF5 root group
+...
++- Step#<i>			# HDF5 group
+   |
+   +- Block			# HDF5 group
+      |
+      +- <field name>		# HDF5 group
+         |
+         +- 0			# HDF5 dataset, first dim of vector
+	 +- 1			# HDF5 dataset, second dim of vector
+         ...
+        +- n-1			# HDF5 dataset, last dim of vector
+...
+
+2.2.5.2 m-rank fields with scalar values
+
+Fields with scalar values are stored as special case of fields with
+n-dimensional vector values with n := 1.
+
+/				# HDF5 root group
+...
++- Step#<i>			# HDF5 group
+   |
+   +- Block			# HDF5 group
+      |
+      +- <field name>		# HDF5 group
+         |
+         +- 0			# HDF5 dataset, scalar value
+...
+
+
+2.3    Step properties [NEW]
+
+Why? Much faster than step attributes if you need to access consecutive values
+
+Group of root group with name "StepProperties"
+
+Members are datasets
+
+Supported values are the same as for step attributes
+
+Mapping of value to step via object index of step group
+

doc/Makefile.am

+EXTRA_DIST = \
+	Doxyfile doxyfooter

doc/doxyfooter

+</BODY>
+</HTML>

license.txt

+*** License agreement ***
+
+H5Part  Copyright (c) 2006, The Regents of the University of California, through Lawrence Berkeley National Laboratory (subject to receipt of any required approvals from the U.S. Dept. of Energy) and the Paul Scherrer Institut (Switzerland).  All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+(1) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+(2) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+(3) Neither the name of the University of California, Lawrence Berkeley National Laboratory, U.S. Dept. of Energy, Paul Scherrer Institut (Switzerland) nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+You are under no obligation whatsoever to provide any bug fixes, patches, or upgrades to the features, functionality or performance of the source code ("Enhancements") to anyone; however, if you choose to make your Enhancements available either publicly, or directly to Lawrence Berkeley National Laboratory, without imposing a separate written license agreement for such Enhancements, then you hereby grant the following license: a  non-exclusive, royalty-free perpetual license to install, use, modify, prepare derivative works, incorporate into other computer software, distribute, and sublicense such enhancements or derivative works thereof, in binary and source code form.
+
+*****

src/H5BlockPrivate.h

+#ifndef __H5BLOCKPRIVATE_H
+#define __H5BLOCKPRIVATE_H
+
+#define H5BLOCK_GROUPNAME_BLOCK	"Block"
+
+#endif

src/TestUnderscore.f

+c ==============
+c
+c Simple Fortran program works in conjunction with C program
+c to determine how many underscores are generated
+c by the fortran compiler
+c
+c ==============
+
+      program TestUnderscoreF
+      implicit none
+      call FindUnderscores
+      end

test/H5BlockParTestScalarField.pbs

+#!/bin/bash
+#PBS -l size=16
+#PBS -j oe
+
+cd /scratch/agsell/H5Part/test
+yod -np 16 ./H5BlockParTestScalarField -w -g
+

visit_plugins/operators/BinnerFilter/Binner.xml

+<?xml version="1.0"?>
+  <Plugin name="Binner" type="operator" label="Binner" version="1.0" enabled="true" mdspecificcode="false" onlyengine="false" noengine="false" iconFile="icon.xpm">
+    <Attribute name="Binner" purpose="Bin particles" persistent="true" exportAPI="" exportInclude="">
+      <Field name="dim1" label="dim1" type="int">
+      </Field>
+      <Field name="dim2" label="dim2" type="int">
+      </Field>
+      <Field name="dim3" label="dim3" type="int">
+      </Field>
+    </Attribute>
+  </Plugin>