On Wed, 21 Oct 2009, Roy Stogner wrote:
> Still not sure what the nonconforming object sizes problem is; I'm
> recompiling with a debug-mode PETSc now.
It appears that I was being overly aggressive about keeping
SNES objects around; PETSc tried to reuse the same ILU preconditioner
which led to e
On Tue, 20 Oct 2009, Andrea Hawkins wrote:
Strange... So, when running it through the debugger I first saw that the type
was AUTOMATIC. To double check, I tried running it again and had
trouble with the debugger. So, I did a make clean, retried and then
subsequently got the error you were rep
Strange... So, when running it through the debugger I first saw that the
type was AUTOMATIC. To double check, I tried running it again and had
trouble with the debugger. So, I did a make clean, retried and then
subsequently got the error you were reporting, the nonconforming object
sizes.
AH! I had
On Tue, 20 Oct 2009, Andrea Hawkins wrote:
> Perhaps the difference is our PETSc versions? I'm using an older one,
> 2.3.3-p13.
2.3.3-p15 is what I'm configured for at the moment...
Could you run your setup through the debugger and see what it says the
vector type is? It sounds like there's g
>
> Good thing you caught this today, too - the new adjoints API (that I
> haven't committed to SVN yet) "helpfully" creates adjoint solutions,
> etc. if they're requested and if they don't already exist. I'd
> intended this to make things easier for user code, but if it had
> already been in plac
On Tue, 20 Oct 2009, Andrea Hawkins wrote:
> I am wanting to implement a similar automatic adaptivity scheme as is in
> example 18. However, in testing the example itself I've run into a few
> issues.
>
> 1. If in the ex18.in file, the global tolerance is set to anything nonzero,
> the code break
