[Dune] [#1018] RFC Patch: allow different convergence criteria in dune-istl

Dune flyspray at dune-project.org
Wed Jan 18 10:34:01 CET 2012


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1018 - RFC Patch: allow different convergence criteria in dune-istl
User who did this - Andreas Lauser (andlaus)

----------
Hi Carsten,

I agree that the proposed API is quite ad-hoc and that it would be better to have a general concept, but I would like to use a fix-point criterion now because I get major performance and minor stability improvements by using it. (Baking it directly into the solvers, would IMHO obfuscate the solvers code quite a bit and would lead to a lot of code duplication.)

If you think it is better than the proposed interface, I will modify the patch so that the update() methods also get the solver object as an argument. Since there are currently no "IterationState" objects, passing solver specific data in a generic way is a problem in the current ISTL implementation. Though it would be possible to define a solver-specific API (e.g. CGConvergenceCriterion) and to provide a wrapper to a "generic" API for each solver.

Finally, and only tangentially related to this discussion, it would be nice if it was possible to declare APIs as experimental which could be defined as "may break without notice".
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1018#comment3034

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.




More information about the Dune mailing list