Viewer+HDF5: Allow reading string attributes
Viewer+HDF5: Now attributes can be associated with an arbitrary objectContributed-by: Mari Pecha <marek.pecha@vsb.cz>
Update to MPI-2.0 versions of attribute interfacesSome of these interfaces were removed in MPI-3. This compiles cleanlywith Open MPI 3.0 and is clean according to the style checks. src/contrib
Update to MPI-2.0 versions of attribute interfacesSome of these interfaces were removed in MPI-3. This compiles cleanlywith Open MPI 3.0 and is clean according to the style checks. src/contrib/style/checks/mpi3-removed-all.sh src/contrib/style/checks/mpi3-deprecated-all.sh
show more ...
convert MPI_Keyval_create() usage to MPI_Comm_create_keyval() and fix error routines from keyval functonsCommit-type: style-fix
Free the MPI Keyval that may have been created during a runProblem located by building MPICH with the option --enable-error-messages=allCommit-type: style-fixFunded-by: ECPTime: .45 hoursRe
Free the MPI Keyval that may have been created during a runProblem located by building MPICH with the option --enable-error-messages=allCommit-type: style-fixFunded-by: ECPTime: .45 hoursReported-by: Daniel Alejandro Ibanez <daibane@sandia.gov>Development Tools: Vim, Emacs, Eclipse
Minor cleanup, remove some outdated code, remove unneeded constructs, improve manual pages slightly, add missing test caseTime: 2.5 hours
Remove the use and definition of __FUNCT__ throughout the codeSince all modern C/C++ compilers provide this functionality we no longer need to provide it manually in PETScTime: 1.5 hoursThanks-t
Remove the use and definition of __FUNCT__ throughout the codeSince all modern C/C++ compilers provide this functionality we no longer need to provide it manually in PETScTime: 1.5 hoursThanks-to: Andreas Mang <andreas@ices.utexas.edu>
Updated and simplified Fortran interfaceReduced from 4 distinct approaches to using PETSc from Fortran to 1No more .h90 files (Fortran 90 functionality is now always available)Parameters and func
Updated and simplified Fortran interfaceReduced from 4 distinct approaches to using PETSc from Fortran to 1No more .h90 files (Fortran 90 functionality is now always available)Parameters and function prototypes are now provide through Fortran modules, not includes;only #define are provided in the petscXXXdef.h filesPETSc objects can be declared as either type(tXXX) or XXX. For example type(tVec) or VecMoved now private Fortran include files out of public include directory since uses don't use them;they are only used to generate the Fortran modulesEasier to support and test; we can now easily add more function prototypesAlso had to rework generation of manual pages to consistently use MANSEC and SUBMANSECsince these variables also handle how the Fortran modules are generated.Time: 57 hours
added manual pages for missing PETSCVIEWERXXX such as PETSCVIEWERBINARYThanks-to: apostol <apostol.faliagas@gmail.com>
replace uses of PetscMalloc() with PetscNew() or PetscMalloc1() where appropriate
PetscViewerHDF5: destroy old file data if setting new filenameI'm just mimicking the _Binary implementation, but I think I all I have to do is H5Fclose the file_id
PetscViewer HDF5: added get name method
Add some missing Fortran wrappers for the PetscViewer functions.* Added PetscViewerGetType and PetscViewerFileGetName* Added HDF5WriteAttribute, HDF5ReadAttribute, HDF5HasAttribute* Enabled HDF5B
Add some missing Fortran wrappers for the PetscViewer functions.* Added PetscViewerGetType and PetscViewerFileGetName* Added HDF5WriteAttribute, HDF5ReadAttribute, HDF5HasAttribute* Enabled HDF5BaseDimension2 and HDF5SPOutput setters and getters
Deprecate PetscViewerSetFormat() since it better to use PetscViewerPush/PopFormat() and usingPetscViewerSetFormat() can lead to confusing situations for users when later viewers do not recognize the
Deprecate PetscViewerSetFormat() since it better to use PetscViewerPush/PopFormat() and usingPetscViewerSetFormat() can lead to confusing situations for users when later viewers do not recognize the setformat and thus do not produce any information.Reported-by: Jed Brown <jed@jedbrown.org>
Begin renaming the PetscOptions objects for the future where PetscOptions will not be a singleton
Add the possibility of writing HDF5 data in single precisionThis commit adds the possibility for the user, at run-time,select to write single precision data into the HDF5 file.This is useful in m
Add the possibility of writing HDF5 data in single precisionThis commit adds the possibility for the user, at run-time,select to write single precision data into the HDF5 file.This is useful in many cases, as one often stop the (iterative)solver when an approximate answer is found, thus not utilizingfull double precision. Using single precision for IO can thensave you half the disk space (or give you the possibility ofwriteing twice the amount of data on the same space).The HDF5 library takes care of the type conversion, hence therequired changes to the IO routines are very small.
updated PETSc directory layout to match standard packaging strategiesinclude/petsc finclude,private,mpiunilib/petsc confbin/petsc*
PETSc Vecs with a bs of 1, coming from a generic VecCreate() or DMCreateGlobalVector() with a DMDAwill NOT have an extra dimension attached to them in HDF5 files created with VecView() with HDF5 vie
PETSc Vecs with a bs of 1, coming from a generic VecCreate() or DMCreateGlobalVector() with a DMDAwill NOT have an extra dimension attached to them in HDF5 files created with VecView() with HDF5 viewers,to have that extra dimension even if the bs is on use either PetscViewerHDF5SetBaseDimension2() or-viewer_hdf5_base_dimension2. Similarly to handle VecLoad() you need to set this value in the viewer if thefile has the extra dimension
manual merge of conflict
moved the rest of the HDF5 calls behind PetscStackCall's
added PetscStackCallHDF5() and test usage
Sys: PetscCheckPointer PETSC_CHAR checks char*, not char**
Fix spurious -Wmaybe-uninitialized warnings
Viewer+HDF5: Avoid HDF5 errors when checking for attributes- How in the HELL can a major software package print DIRECTLY to the screen even when I am catching the error. You Suck HDF5!
Viewer+HDF5: Added PetscViewerHDF5HasAttribute()
12345678910