fixes for PETSc threadsafety changes when threadsafety is not turned on
fixes for missing ierr = around PetscLogFlops()
initial locks with concurrencykit and OpenMPcleanup of many monitors that used nonthread safe constructors when no viewer passed incleanup of examples that generated unused variable messages when
initial locks with concurrencykit and OpenMPcleanup of many monitors that used nonthread safe constructors when no viewer passed incleanup of examples that generated unused variable messages when compiled with --with-log=0
show more ...
merged PetscViewerGetSingleton() and PetscViewerGetSubcomm() into PetscViewerGetSubViewer()Does not currently work, needs fixes to work correctly recursively
updated manual pages for external direct solvers to explicitly state how to configure PETSc for them and to run with them with KSP
Merged in PR312: karpeev/ksp-pcgasm-overhaul.
bugs in example that should never have gotten into nextbug in code calling VecGetArray() on read only vector
Merge branch 'maint'
Fix nonzerostate tracking in all MATMPI types.
Infrastructure that allows failures in PCSetUp(), PCApply(), MatMult() etc due to, for example a zero pivot or function evaluation outside its domain, to propagate up and become a KSP_DIVERGED inste
Infrastructure that allows failures in PCSetUp(), PCApply(), MatMult() etc due to, for example a zero pivot or function evaluation outside its domain, to propagate up and become a KSP_DIVERGED instead of generating an error that stops the program. In response to Issue 96. This includes failures in MatCreateSNESMF() applications due to domain errors. The mechanism to propagate some errors is by setting Info or Nan into the output vector and using the norm or inner product reductions in SNES or KSP to propagate the error condition to all processes and then handling them immediately after the norm or inner product.This allows, for example, ODE integrators to try again with a smaller time-step if the PCSetUp failed instead of requiring a complete restart of the run with other options.Currently some error conditions, such as function domain error in a line search may not get progated up using the correct SNESConvergedReasonSee src/snes/examples/tests/ex69.c for the handling of several conditions
MatGetSubMatricesParallel —> MatGetSubMatricesMPI. Implementation rewritten, tests added.
updated PETSc directory layout to match standard packaging strategiesinclude/petsc finclude,private,mpiunilib/petsc confbin/petsc*
rm unused variables
rm 'statement not reached' -- reported by PETSc blame digest
Merge branch 'tisaac/mat-get-submatrix-unordered'
Merge branch 'barry/fix-matload-uneven-rows'Conflicts: src/mat/examples/tests/makefile
MatLoad_MPIXAIJ() did not work correctly with user provided decomposition of the matrix rowsalso added test example for this case
Optimized MatShift() for a completely empty matrix since this is commonly used with SLEPc to produce diagonal matricesReported-by: Jose Roman <jroman@dsic.upv.es>
Merge branch 'barry/add-casts-for-suitsparse-64bitindices'Conflicts: src/ksp/ksp/examples/tutorials/makefile
MatSetValuesMPISBAIJ will now print correct global indices when errorgenerated due to new nonzero location
in error messages in MatSetValuesBlocked_Seq(S)BAIJ clarify the indices are block not point
clarify in error messages for MPI Mat block set values that the printed indices are block based, not point based
When generating error new nonzero location in MatSetValues_MPIxxx() calls print the global row/column number of the offending locationPreviously this printed the number inside the local sequential p
When generating error new nonzero location in MatSetValues_MPIxxx() calls print the global row/column number of the offending locationPreviously this printed the number inside the local sequential portion of the matrix which is confusing for usersNote that this cannot be done trivially for MatSetValuesBlocked_MPIxxx() because the insertion in the submatrix is in a seperate function that does not know about the calling function
Since SuiteSparse uses long for 64 bit indices and PETSc uses long long some compilers warn about non-matching types (even though everything is fine)Add castes to SuiteSparse calls to prevent warnin
Since SuiteSparse uses long for 64 bit indices and PETSc uses long long some compilers warn about non-matching types (even though everything is fine)Add castes to SuiteSparse calls to prevent warningsAlso fix several nightly build output files to prevent noise in testing
suitesparse: use (upstream) build defaults - and not change SuiteSparse_long during build (by PETSc).Also remove UF_long usage in code [this was out of sync with UF_long -> SuiteSparse_long change
suitesparse: use (upstream) build defaults - and not change SuiteSparse_long during build (by PETSc).Also remove UF_long usage in code [this was out of sync with UF_long -> SuiteSparse_long change in SuiteSparse.py]Add error message when using 64-bit-indices on 32bit machines (as its not supported by default suitesparse build)
1...<<11121314151617181920>>...69