Hi!
The version 0.6.4 does not support "component_scale" to scale (and to choose)
the variables to calculate the error norm wich is used by the error estimator
for AMR/C as the 0.6.3 version does.
How to reproduce the scaling error through the "SystemNorm error_norm"
(error_estimator.h) for
On Fri, Sep 17, 2010 at 9:00 AM, Roy Stogner wrote:
> Derek's lazy? ;-)
>
LOL - That usually is the case... but in this case I think it was just lack
of diligence. I don't remember thinking "meh I'll just leave those out"...
I actually just didn't think of them at all ;-)
Me being lazy is alwa
On Fri, 17 Sep 2010, Tim Kroeger wrote:
> Thank you for this hint. Using this, it was easy to find the point where the
> macro is not called. It's in libMesh, however, that is in
> petsc_preconditioner.C, line 49. Actually, in that file, a lot of calls to
> CHKERRABORT() are missing. Roy,
On Fri, 17 Sep 2010, Jed Brown wrote:
> On Fri, Sep 17, 2010 at 16:35, Tim Kroeger
> wrote:
>> Can you (Jed) comment on how it can happen that KSPSolve() prints this error
>> message but nicely returns 0?
>
> CHKERRQ is not being called somewhere in the stack, if it's in PETSc
> code, please let
On Fri, Sep 17, 2010 at 16:35, Tim Kroeger
wrote:
> Can you (Jed) comment on how it can happen that KSPSolve() prints this error
> message but nicely returns 0?
CHKERRQ is not being called somewhere in the stack, if it's in PETSc
code, please let me know where it is (or send a full trace).
As a
I'm currently testing my application with the new subset stuff, and
I'm observing some PETSc behaviour that I find strange. At some place
in petsc_linear_solver.C, I do:
ierr = KSPSolve (_ksp, subrhs, subsolution);
CHKERRABORT(libMesh::COMM_WORLD,ierr);
What now happens is that
