removed unneeded { around SETERRQX() calls}

Hg-commit: d55148dbbe8a10f500a7e181b91ba166aec6f665

merge from release

Hg-commit: 0a243b58bcc67382f0974df4db9343f8c7c5e794

commit after merge

Hg-commit: a943693fc1dc75fc6929b1e3c8d2179e228e3223

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 ...

Two SETERRQs not given communicator, use PC communicator since these are options database compatibility checks

Hg-commit: 03b0678a4b1913290be970855566dd31cbcaef51

add patch contributed by lawrence.mitchell@ed.ac.uk (see [petsc-maint #45870] PCSetUp_ML needs to set communicator )

Hg-commit: 00a52a8194d242ac0ff263979c726708bd2a7865

added MPI_Comm as first argument to PetscError() and SETERRQX()

Hg-commit: fe5a2ff050abc00ca2c2979c0af22b117b62874e

From: jed@59A2.org
Subject: [petsc-dev] DD FAQ
Date: April 26, 2010 9:03:26 AM CDT
got a PCExotic example working, mentioned it in faq.html and put back mention of PCNN

Hg-commit: 6a4342060cbce9

From: jed@59A2.org
Subject: [petsc-dev] DD FAQ
Date: April 26, 2010 9:03:26 AM CDT
got a PCExotic example working, mentioned it in faq.html and put back mention of PCNN

Hg-commit: 6a4342060cbce94fcef0615863f59fed456363fb

show more ...

when shifttype == MAT_SHIFT_NONZERO, set default shift amount 1.e-12 if user has not set it yet.
Otherwise, numerical factorization might hang. See [petsc-maint #45421] Problem with ICC on SEQBAIJ.

when shifttype == MAT_SHIFT_NONZERO, set default shift amount 1.e-12 if user has not set it yet.
Otherwise, numerical factorization might hang. See [petsc-maint #45421] Problem with ICC on SEQBAIJ.

Hg-commit: 6bd1da78362808c42df203374dbc55aa4b74fd7d

show more ...

bugfix for -pc_factor_shift_type nonzero.
(see [petsc-maint #45421] Problem with ICC on SEQBAIJ)

Hg-commit: c6c6f641c1bbfbd11575aaba0155c7b59a657064

fixed bad charactor that got into file

Hg-commit: 82bfd25d73eade8c618f858a0debbc08cf579b49

commit after merge of patch to 3.1 that removed extraneous include "matimpl.h"

Hg-commit: cd6e3c721ebe97497a0385b2e30092de3c1f5f43

some code cleanup and further work on DMMG version 2

Hg-commit: 896f032fd4a8a52f74fc4b043ca1a9059a613c52

PC implementations should not access matimpl.h (the internals of matrices) unless they really need to, removed several unneeded accesses.

Hg-commit: ed08571d0731ceb766180178f75857634f029a0a

commit after merge

Hg-commit: 69f1281a23b9204054fdf5036ff4edc4275b3f87

factimpl.h had an include "matimpl.h" INSIDE a EXTERN_C_BEGIN block, removed the include completely
needed to add MatGetFactorType() to not require access inside the Mat struct

Hg-commit: 0bad2c2

factimpl.h had an include "matimpl.h" INSIDE a EXTERN_C_BEGIN block, removed the include completely
needed to add MatGetFactorType() to not require access inside the Mat struct

Hg-commit: 0bad2c2eef385e0f672b0cd77b13f9a4b2b54016

show more ...

general cleanup of petscsys.h
removed PetscStrfree() since PetscFree() does the same thing

Hg-commit: 383ece197d31b92016b12ff3a62a2e744f8d981d

commit after merge

Hg-commit: 34af44ec3a390a8370e6ef8a309b0623ab97ccc0

systematically changed use of phrase of ./config/configure.py to ./configure to have one consistent (and standardish) way of refering to it. Having two ways of refering to the same thing is confusing

systematically changed use of phrase of ./config/configure.py to ./configure to have one consistent (and standardish) way of refering to it. Having two ways of refering to the same thing is confusing and unneccesary

Hg-commit: fcd327f3f4fcb82c63cd1afe8da55ad84e8250f3

show more ...

merge PCFieldSplitSetIS() doc clarification from release

Hg-commit: f5bf4c9f4ae1b6ae322deb9b4cc90c1e59a345e4

Clarify PCFieldSplitSetIS documentation

Hg-commit: ef0f51790be58020b2412670a9e244b673e5b649

fixed KSPSetPreconditionerSide() that was suppose to be KSPGetPCSide()

Hg-commit: 068117fbd4fb4281de7587f212174056f2cf30b1

changed -ksp_right_pc and friends to -ksp_pc_side right,left,symmetric
changed KSPSetPreconditionerSide() to KSPSetPCSide() to match second argument which is PCSide not PreconditionerSide

Hg-commit:

changed -ksp_right_pc and friends to -ksp_pc_side right,left,symmetric
changed KSPSetPreconditionerSide() to KSPSetPCSide() to match second argument which is PCSide not PreconditionerSide

Hg-commit: 80ca67847b9d07b490f4014f7a90ed092dfe28e4

show more ...

Update ML interface to support energy minimization and other options.

This uses many features that are not documented in the reference manual.
In particular, the C interface does not seem to be supp

Update ML interface to support energy minimization and other options.

This uses many features that are not documented in the reference manual.
In particular, the C interface does not seem to be supported any more,
the current one is based on strings and is only available from
C++/Epetra with associated baggage and certain limitations relative to
the C interface. Fortunately, the C++ interface has a nearly one-to-one
correspondence with fields in the ML_Aggregate structure, so the present
code sets options in that structure directly (when not available from
C++).

The biggest problem with exposing this extra functionality is that ML
options are rather non-orthogonal so it's easy to produce options sets
that are not actually functional. Rather than providing useful
(user-understandable) information about what is wrong, ML calls exit(1).
So if ML crashes, you have to attach a debugger with a breakpoint on
'exit' just to get a stack trace (for example, to know which ML instance
in your code is causing trouble). I am less than thrilled with this
error handling strategy.

Hg-commit: e721d2184f87ad8008519982dabd8955327e31f2

show more ...

minor cleanup of users manual
added better support in mapnameslatex.py to make links for more cases of use of manual page names. Previously it excluded everything inside {}

Hg-commit: 72024b997043b7

minor cleanup of users manual
added better support in mapnameslatex.py to make links for more cases of use of manual page names. Previously it excluded everything inside {}

Hg-commit: 72024b997043b739e0d134fd69c9a61c076853ca

show more ...