/pipermail/petsc-dev/attachments/20101201/b8a2d8a1/attachment.html
was scrubbed...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101201/656bd24e/attachment.html
...
[ 87%] Building C object
CMakeFiles/petsc.dir/src/ksp/pc/impls/gasm/ftn-auto/gasmf.c.o
[ 88%] Building C object
CMakeFiles/petsc.dir/src/ksp/pc/impls/composite/ftn-auto/compositef.c.o
/Users/barrysmith/Src/petsc-dev/src/ksp/pc/impls/gasm/ftn-auto/gasmf.c: In
function
We need a really good entry in the FAQ for solving Stokes problems with PETSc
or a solid section in the users manual. This question comes up fairly often
(usually phrased as something like ILU sucks for my problem, what is wrong with
PETSc).
Barry
On Dec 1, 2010, at 8:32 AM, Jed Brown
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101201/8e7618a1/attachment.html
/petsc-dev/attachments/20101201/b824ca0a/attachment.html
After wasting a bunch of Shri's time with my stupidity I realized it would be
great if we could somehow mark PETSc objects to PETSc methods as const in
either the source code and/or the manual pages. Or better yet, not const.
For example the first Vec argument to MatMult() is const but not
Hi Barry,
I have updated the DMGetInterpolation_DA_XXX_Q1() family of
functions to enable them to
work with DMDA's which are nested, but have general coordinates
defined by the user.
The original used code which would compare two floating point numbers
with == and in general it
would seg fault
