| #
79410860
|
| 13-May-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
PCSetOperators() will not generate error if passing in null operators.
added Note to KSPSetOperators() that you cannot change the size of the matrices with future calls
Hg-commit: 7d226c8ba617eca0d3
PCSetOperators() will not generate error if passing in null operators.
added Note to KSPSetOperators() that you cannot change the size of the matrices with future calls
Hg-commit: 7d226c8ba617eca0d310f16a646ad02c07f6af91
show more ...
|
| #
3b3f6333
|
| 13-May-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
do not allow setting a new PCSetOperator() with a different size after it has been used
From: Matthew Knepley <knepley@gmail.com>
Subject: [petsc-maint #46134] Re: [petsc-users] Error usin
do not allow setting a new PCSetOperator() with a different size after it has been used
From: Matthew Knepley <knepley@gmail.com>
Subject: [petsc-maint #46134] Re: [petsc-users] Error using the same ksp with different operator sizes
Date: May 13, 2010 9:57:22 AM CDT
To: Aron Ahmadia <aron.ahmadia@kaust.edu.sa>, petsc-maint Maintenance <petsc-maint@mcs.anl.gov>
Reply-To: petsc-maint Maintenance <petsc-maint@mcs.anl.gov>, Matthew Knepley <knepley@gmail.com>
On Thu, May 13, 2010 at 10:44 AM, Aron Ahmadia <aron.ahmadia@kaust.edu.sa>wrote:
In that case, shouldn't you throw the error when they try to set the new
operator?
Hg-commit: afd8a6ab1b20bc643b64afec12cd81f0ec325471
show more ...
|
| #
65e19b50
|
| 11-May-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
the last work I will do on reformatting use of SETERRQX() and passing in the appropriate comm; I am bored to tears
Hg-commit: 9e0ef782022dbdc055a74473b60f135ee06122ac
|
| #
e7e72b3d
|
| 08-May-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
changed many calls to SETERRQ() to use correct (non-PETSC_COMM_SELF) communicator
reformated many badly formatted SETERRQ(); there was nonsense like {} around them or they were wrongly on a seperate
changed many calls to SETERRQ() to use correct (non-PETSC_COMM_SELF) communicator
reformated many badly formatted SETERRQ(); there was nonsense like {} around them or they were wrongly on a seperate line
Hg-commit: 7550f3779f18eaf7ce68bae52b964532aa97c1d5
show more ...
|
| #
e32f2f54
|
| 07-May-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
added MPI_Comm as first argument to PetscError() and SETERRQX()
Hg-commit: fe5a2ff050abc00ca2c2979c0af22b117b62874e
|
| #
f0eb1ee0
|
| 12-Apr-2010 |
Dmitry Karpeev <karpeev@mcs.anl.gov> |
Merge.
Hg-commit: 96dff560e9caff2ee6539fb4c50e92b67324e0b0
|
| #
fcd96beb
|
| 10-Apr-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
commit after pull of manual pages patches for 3.1
Hg-commit: fdda79b9b0cfa271aff815250a8f6761d22b5ee8
|
| #
834dbeb0
|
| 09-Apr-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
removed PetscObjectExists() very dangerous function, little used
minor manual page fixes
Hg-commit: cb01c277f10bfdc4f569c4aaf2838cbe32ff5320
|
| #
0700a824
|
| 08-Apr-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
changed cookie to classid cause that is what it is.
Hg-commit: ffa25d1edea7afc409fcc13e7f2b63587b1494c1
|
| #
f9a2c96d
|
| 27-Mar-2010 |
Dmitry Karpeev <karpeev@mcs.anl.gov> |
Merge.
Hg-commit: b27e7be9c09691d1f15f4d8d34f1b0fc4ac63ae4
|
| #
af8c88b6
|
| 24-Mar-2010 |
Matthew G Knepley <knepley@gmail.com> |
Merge
Hg-commit: 76530b3bd33348a33ed1676aa7af10e463910250
|
| #
6c699258
|
| 22-Mar-2010 |
Barry Smith <bsmith@mcs.anl.gov> |
added XXXSetDM() and XXXGetDM() for PC,KSP,SNES and TS
Hg-commit: bada9ff4302cce1dee88b5dd282aa59af62f2a84
|
| #
098c0d8d
|
| 24-Sep-2009 |
Matthew Knepley <knepley@mcs.anl.gov> |
Merge
Hg-commit: a7710b011ce3f2c4ac169ab040d429403a541f7f
|
| #
7319c654
|
| 24-Sep-2009 |
Barry Smith <bsmith@mcs.anl.gov> |
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 ...
|
| #
8a88346a
|
| 22-May-2009 |
Matthew Knepley <knepley@mcs.anl.gov> |
Removed BlockSolve95
- It is no longer supported
- ILU functionality is subsumed by PILUT in Hypre
Hg-commit: d675b710d2423988e415bd4d531a95abb123ca4c
|
| #
1e2779b9
|
| 01-Oct-2008 |
Matthew Knepley <knepley@mcs.anl.gov> |
Merge
Hg-commit: 560967f73576a4f69de6214484d8747c4740d79d
|
| #
1a2f9f99
|
| 30-Sep-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
PCApply_MG does not need to check if mg[levels-1]->r exists, it is now ALWAYS set in PCSetUp_MG
Hg-commit: 3664f08236c7bf595f3fb207cfd4da1c766b822a
|
| #
4fc57388
|
| 15-Sep-2008 |
Matthew Knepley <knepley@mcs.anl.gov> |
Merge
Hg-commit: a2f7b9b8efe1825eadceecf27bade4115f4c35a5
|
| #
db4efbfd
|
| 15-Sep-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
moved assignment of LUFactorNumeric and CholeskyFactorNumeric into appropriate symbolic factorization (previously it was set
in the function table or in the getfactor
moved assignment of solve() i
moved assignment of LUFactorNumeric and CholeskyFactorNumeric into appropriate symbolic factorization (previously it was set
in the function table or in the getfactor
moved assignment of solve() into appropriate numeric factorization, previously it was in function table or get factor or symbolic factor
Hg-commit: 83ba8e21d43889fe945455ea7c1fb95368f1a281
show more ...
|
| #
189c0b8a
|
| 08-Sep-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
added petscapp.bib pub
Hg-commit: 98227e0e771a8e736c3f38b40d1fba4a54925a11
|
| #
7f6cc9d5
|
| 05-Sep-2008 |
Hong Zhang <hzhang@mcs.anl.gov> |
merge
Hg-commit: e1af96f3ec0cf9f5c1f85ab200a7e8fb6ed87c3b
|
| #
4d0a8057
|
| 15-Aug-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
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 ...
|
| #
fd5f9c01
|
| 01-Aug-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
commit after merge
Hg-commit: 40fbcb1ffa2ac14ad5b1cd85db9cdd19834e6819
|
| #
9b3038f0
|
| 31-Jul-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
tentative working version of ibcgs
Hg-commit: de0dbdc36195e8aaaafee5ef5ba612be2c7c55d9
|
| #
207126cb
|
| 23-Jul-2008 |
Barry Smith <bsmith@mcs.anl.gov> |
commit after most of merge of petsc-dev with petsc-dev-new-solvers with new way of handling external solvers
Hg-commit: 7c86fa28bc8468b955cc6a62edd1de55d6c3d700
|