Merge

Hg-commit: a7710b011ce3f2c4ac169ab040d429403a541f7f

PCApplyRichardson() now takes a flag indicating if initial guess is zero, this saves work on application of SOR preconditioner in first iteration for example
KSPSolve() checks if the norm of x is kno

PCApplyRichardson() now takes a flag indicating if initial guess is zero, this saves work on application of SOR preconditioner in first iteration for example
KSPSolve() checks if the norm of x is known to be zero and if so temporarily sets the guess_zero flag in KSP (it is only temporarily cause in the next solve it may not be zero.

Hg-commit: 7c18a45dad7e4c7bb780a7cf7ffbc18bb03598c8

show more ...

Merge
- Watch out for SNES ex45, I think the merge was bad

Hg-commit: 04bc4bca24f51d95f00a035b6b5fb2e5990fd8a8

Fix typo: gride -> grid

Hg-commit: 9253269d71d222e7744ca37c877320c81f69732e

changed PetscOptionsName() and PetscOptionsHasName() to return true if option is set, regardless of the value it is set to, include 0 and false
changed most uses of these routines to the Truth vari

changed PetscOptionsName() and PetscOptionsHasName() to return true if option is set, regardless of the value it is set to, include 0 and false
changed most uses of these routines to the Truth varient

Hg-commit: fd6366abd7eb1f3ec925faa0ecd078d5cc025eb2

show more ...

merge

Hg-commit: c7c983b1db57f8ad4e014f17b4caeff6d19e55af

PCMGMCycle_Private() called the coarse solver twice in a row with w cycle

Hg-commit: c1ade4b84db0ee6969d7c3cd4ecef67163f668ec

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: e02bd69d1e9b73f5c8d61e83da411f12f8cb9e16

merge

Hg-commit: d58f70d4c7f7a3dcf9b566c82063e66c58e67ce4

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: af487d5b45dae01d0566132d57158d0286d6a750

removed -I$PETSC_DIR from make system and changed the corresponding
#include "src/dsdsdsds" to "../src/sdsdsds" in the source code

Hg-commit: 6e3c4cc4b4bfcb366bae9b71afcb5009c1f0429d

Merge

Hg-commit: 560967f73576a4f69de6214484d8747c4740d79d

PCApply_MG does not need to check if mg[levels-1]->r exists, it is now ALWAYS set in PCSetUp_MG

Hg-commit: 3664f08236c7bf595f3fb207cfd4da1c766b822a

added most of the appropriate PetscObjectIncrementTabLevel() calls on KSP objects

Hg-commit: 55ad623694bf2fcd3544ef7f480b24298f32bf4c

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 most of merge of petsc-dev with petsc-dev-new-solvers with new way of handling external solvers

Hg-commit: 7c86fa28bc8468b955cc6a62edd1de55d6c3d700

Merge

Hg-commit: acacbb5449cb3c4529d96c934fe48fa4c267f6ac

commit after merge

Hg-commit: b094826e5478ecc96e25cb0a3646768807141858

over reference counted vector in PCMG

Hg-commit: 931674f91712db08278257e6ef13c4d3ed8432f5

merge from release

Hg-commit: 29b1d3527c7e02e50b402d8643da29a34282c6ae

#17858 fix memory leak

Hg-commit: 7c338cfe5286d1d7c3e1723c646a9bcd7da17f37

commit after merge

Hg-commit: 585879f5445257acbb9951c7861f508377f1f645