Convert MPI error type to PETSc error with string message for all MPI callsNow PETSc examples will ONLY return PETSc error codes and never MPI error codes directly so we can understand and post-pro
Convert MPI error type to PETSc error with string message for all MPI callsNow PETSc examples will ONLY return PETSc error codes and never MPI error codes directly so we can understand and post-process their errors better.The test harness will now automatically retry tests that fail with MPI, this may help with Intel MPI that produces seemingly random failures.Commit-type: error-checking/spend 30m
show more ...
Most external factorization packages do not use the ordering provided by PETSc, therefor only provide it when needed.Adds MatOrderingType external to indicate not to generate an ordering and use wh
Most external factorization packages do not use the ordering provided by PETSc, therefor only provide it when needed.Adds MatOrderingType external to indicate not to generate an ordering and use what the package needsNow -pc_view will not print the wrong PETSc ordering when the ordering is done externallySaves some memory and compute time.Commit-type: optimizationTime: 1.2 hoursReported-by: Junchao Zhang <junchao.zhang@gmail.com>Thanks-to: Stefano Zampini <stefano.zampini@gmail.com>
Single petscdir.mk
build: add more support for not needing to set PETSC_DIR yet build with PETSc, also support for GNU make to directly use "make test" instead of "make -f gmakefile.test"Still needs -include ../petsc
build: add more support for not needing to set PETSC_DIR yet build with PETSc, also support for GNU make to directly use "make test" instead of "make -f gmakefile.test"Still needs -include ../petscdir.mk in many of the makefilesStill needs the link for ../petscdir.mk in many directoriesGNUMakefile: call legacy makefile recursively instead of including itGNUMakefile: promote default "all" target; "libs" builds libpetsc*GNUMakefile: If gnumake < 4.2 prefer makefile wrapper interface over direct gmakefile interface to avoid the following warningsgmakefile.test:92: arch-ci-linux-cxx-cmplx-pkgs-64idx/tests/testfiles: No such file or directorygmakefile:67: arch-ci-linux-cxx-cmplx-pkgs-64idx/lib/petsc/conf/files: No such file or directoryCommit-type: testing-fix, feature, usabilityThanks-to: Jed Brown jed@jedbrown.org
Add PetscArraycmp(), PetscArraycpy(), PetscArrayzero(), PetscArraymove(), update code to use new formsReplace a couple multi-mallocs with a single mallocReplace backwards loops in MatSetValues_*()
Add PetscArraycmp(), PetscArraycpy(), PetscArrayzero(), PetscArraymove(), update code to use new formsReplace a couple multi-mallocs with a single mallocReplace backwards loops in MatSetValues_*() with PetscArraymove()Commit-type: style-fix, feature
Revert the function name where it is referenced
Changed VecScatterCreate() to take a communicator and return scatter as other first class PETSc objects do.Changed old VecScatterCreate() to VecScatterCreateWithData()Completed basic refactorizati
Changed VecScatterCreate() to take a communicator and return scatter as other first class PETSc objects do.Changed old VecScatterCreate() to VecScatterCreateWithData()Completed basic refactorization of VecScatter code, ready for new implementations to be added.(There is still some code duplication between the VecScatter MPI1 and MPI3 code but it can be fixed at anytime without requiring changes to the VecScatter API.Part 5 of a refactorization of VecScatter to be treated as a first class PETSc objectCommit-type: style-fix
Man pages: add newlines after "Notes:"This allows for proper formatting from sowing.On OS X (using gsed, not the default BSD sed), from the PETSc root directory: find src include -type f \(
Man pages: add newlines after "Notes:"This allows for proper formatting from sowing.On OS X (using gsed, not the default BSD sed), from the PETSc root directory: find src include -type f \( -name "*.c" -or -name "*.h" -or -name "*.cxx" \) | xargs gsed -i 's/Notes\s*:\s*\(\w.*\)/Notes:\n \1/'This adds a newline and 4 spaces whenever "Notes:" is followed by any "word" character, in any .c, .h, or .cxx file in src/ or include/
change MatSolverType to be a const char* typedef to match other XXTypeCommit-type: style-fixReported-by: Franck Houssen <franck.houssen@inria.fr>
Fix name MatSolverPackage since it is better to be consistent and use the terminology Type.Commit-type: style-fix, documentation
Merge branch 'maint'
fix typo in manual page that propogated with cut and paste to many manual pagesCommit-type: documentationReported-by: apostol <apostol.faliagas@gmail.com>
Fix dimension errors in PasTix interface, add more error checking. Remove useless checkmatrix codeCommit-type: bug-fixReported-by: GONG Ding <gongding@cn.cogenda.com>
Pastix: do not use MPI_COMM_WORLD
rename MatGetSubMat -> MatCreateSubMat
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>
Merge remote-tracking branch 'origin/maint'
pastix: some build issues are fixed in the latest releaseTime: .1hReported-by: "Garth N. Wells" <gnw20@cam.ac.uk>Reported-by: Pierre Jolivet <pierre.jolivet@enseeiht.fr>
Refactored ./configures handling of package requirements for precision. Now each package indicateswhat it supports withself.precisions = ['single','double','__float128']Updated the package files t
Refactored ./configures handling of package requirements for precision. Now each package indicateswhat it supports withself.precisions = ['single','double','__float128']Updated the package files to indicate what they supportRemoved unneeded #requires arguments from makefiles for external packages.Time: 2 hoursReported-by: Patrick Sanan <patrick.sanan@gmail.com>
fixed PASTIX to not use spptrAlso fixed memory leaks in PASTIX for parallel solves
Fix null output from PCFactorGetMatSolverPackage();Reported-by: Jose E. Roman <jroman@dsic.upv.es>
More decreasing visibility of symbols from outside librariesAlso fix a few bugs related to having multiple PETSc libraries
Complete update to new PetscOptions interface
updated manual pages for external direct solvers to explicitly state how to configure PETSc for them and to run with them with KSP
updated PETSc directory layout to match standard packaging strategiesinclude/petsc finclude,private,mpiunilib/petsc confbin/petsc*
123456