Support for dynamically embed Python and use petsc4py

Hg-commit: a45d78b8f61d623c0579617c9e88faa63956e4c1

Merge

Hg-commit: 3a05a9a21fcd66acdc0680d4c36ce9e8f08fa147

completed first generation of PCEXOTIC with support for a face and a wirebasket based
coarse grid space; ready for testing with pflotran

Hg-commit: 429f53fb595cd45cf53abcc3b513c1f769ef5a7f

Merge

Hg-commit: 07349036822f6f1587b216c0375ab8a63c27eb25

improvements for PCASM and add PCASMCreateSubdomains() based on MatPartitioning

Hg-commit: 96ae51932456ee0f1000bb20cae78557f188a84c

Merge

Hg-commit: e02bd69d1e9b73f5c8d61e83da411f12f8cb9e16

merge

Hg-commit: d58f70d4c7f7a3dcf9b566c82063e66c58e67ce4

moved declaration of PCWBSetDA to petscmg.h because petscpc.h does not
know about DA/DM

Hg-commit: 3384c9ace99eaa704597967d7410d83d1d1129bc

From: mstefano@milan.westerngeco.slb.com
Subject: [Fwd: Re: [PETSC #18599] Valgrind problem with MatGetSubMatrix]
Date: November 14, 2008 2:30:37 AM CST
To: petsc-maint@mcs.anl.gov
Cc: pets

From: mstefano@milan.westerngeco.slb.com
Subject: [Fwd: Re: [PETSC #18599] Valgrind problem with MatGetSubMatrix]
Date: November 14, 2008 2:30:37 AM CST
To: petsc-maint@mcs.anl.gov
Cc: petsc-maint@mcs.anl.gov

I think I've found the bug.

Look at src/mat/impls/aij/seq/aij.c, line 1699.

There, variable "i" is declared as a PetscInt.

Then, look at line 1710 or 1712.

The variable "i" is used to get the truth answer from the ISSorted function.

As long as you don't build PETSc with --with-64-bit-indices, all is OK.

But (and this is my case) if you built PETSc with 64 bit indices, the PetscTruth data type is smaller (as byte size) than PetscInt. The result is that only part of the bytes of the "i" variable are initialized by ISSorted.

I strongly suggest to add a new variable to be used exclusively as a PetscTruth flag for the ISSorted calls.

Fixed this bug all over the place

Hg-commit: 79369c761f62f38e25800abc8725233db2a5486a

show more ...

Merge

Hg-commit: 272825bf90eb39df4965e7226316ed8f305bd52c

merge

Hg-commit: 408642326083bdab3b0d21e98f912dfddb31927e

* Using MUMPS, MatGetInfo(...,&info), info.nz_allocated is given for the
initial matrix (not the factorized one). Currently I use :
- Mat_MUMPS *lu=(Mat_MUMPS*)mat->spptr;
- lu->id.INFOG(20)
to get

* Using MUMPS, MatGetInfo(...,&info), info.nz_allocated is given for the
initial matrix (not the factorized one). Currently I use :
- Mat_MUMPS *lu=(Mat_MUMPS*)mat->spptr;
- lu->id.INFOG(20)
to get the same information. It's a dirty solution...

Added MatFactorGetSolverPackage(), also properly printed with -mat_view_info and -ksp_view

Hg-commit: d45534d976bbd57e4a4d4c4173150bb1403ccc76

show more ...

Registered BFBt PC

Hg-commit: 11a138bc23ced53264aeee2301eec9f95dcae63c

commit after merge; lots of GU conflicts needed to be resolved, why? I don't know, most looked
like they could be done automatically

Hg-commit: 2b292236ee5585a41c97ddcafd3f409331a1dd72

Added a method for Schur complements with FieldSplit

Hg-commit: 1d0a88c39c8a77737f69a9a3896999ff0b1b8941

basic Schur complement solver works for parallel
KSPMonitorDefault() will now print name of suffix at beginning of iteration if suffix exists.

Hg-commit: 2d03aa35d2b8b97db310359e50d7c8c88722efe0

basic Schur complement preconditioner is now working (no preconditioner on the Schur solve yet)

Hg-commit: b92a24fa5a99cb9f0f1ebe423a22c2cab0402a12

When KSPRICHARDSON is used without a KSP monitor and the PC has a PCApplyRichardson() then
ksp->its and converged reason are properly set to indicate type of convergence.

Also with HYPRE BoomerAMG

When KSPRICHARDSON is used without a KSP monitor and the PC has a PCApplyRichardson() then
ksp->its and converged reason are properly set to indicate type of convergence.

Also with HYPRE BoomerAMG when used as a solver (with KSPRichardson) the KSP convergence
criteria is passed down to BoomAMG and replaces the default (usually 0.0) criteria we normally
pass to BoomerAMG (for when we use BoomerAMG as a preconditioner.

Keita,

Thanks for pointing this out. This is a "feature" of some of the preconditioners when used with
Richardson. We call the preconditioner with a number of iterations directly and the preconditioner
decides when to exit (rather than all other cases where KSP decides), hence we did not have
information about the number of iterations. So in previous versions we did not set the ksp->its;
petsc-dev was changed to set ksp->its to the maximum number of iterations requested in the
preconditioner.

This too is not really correct because some preconditioners when used with Richardson
(specifically PCMG and hypre's BoomerAMG) will do the convergence test internally and
may not use the maximum number of iterations requested. I will modify petsc-dev today to
collect this information back from the preconditioner and pass it back correctly to ksp->its.

Hg-commit: d8d04f2052ab2294999b137bb681449db81389c7

show more ...

commit after merge

Hg-commit: 40fbcb1ffa2ac14ad5b1cd85db9cdd19834e6819

changed MatSolveType to MatSolverPackage

Hg-commit: 237da6d33a71fc726cd7c44ec309405456f8c5c8

added PCFactorSetMatSolverType()

Hg-commit: eb459177ef24a54b63ec70034319fe5ddf31ab25

commit after most of merge of petsc-dev with petsc-dev-new-solvers with new way of handling external solvers

Hg-commit: 7c86fa28bc8468b955cc6a62edd1de55d6c3d700

Merge

Hg-commit: 41800043acaea4edc1ffe515ad0d33298e6b8178

commit after merge

Hg-commit: e601a1d4489b52dd4b994bcbaede554178eb5e2c

moved the const out of XXType definitions and into the Set and Get Methods

Hg-commit: d4d9a237045a151847ef3121b00df73d952d0999