commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles (JIRA)" <>
Subject [jira] [Created] (MATH-799) Remove default values for tolerances in "AbstractConvergenceChecker"
Date Sun, 03 Jun 2012 23:21:23 GMT
Gilles created MATH-799:

             Summary: Remove default values for tolerances in "AbstractConvergenceChecker"
                 Key: MATH-799
             Project: Commons Math
          Issue Type: Task
    Affects Versions: 3.0
            Reporter: Gilles
            Assignee: Gilles
            Priority: Trivial
             Fix For: 3.1, 4.0

The custom convergence checkers let users override the ad-hoc convergence criteria that most
optimization algorithms provide.
CM defines "simple" checkers that inherit from "AbstractConvergenceChecker" and use the default
values provided in that class. However good values for the tolerances are problem-dependent.
User control cannot come without the user paying attention to those values, or "strange" failures
can happen (cf. issue MATH-798).

It is thus proposed to remove the default values defined in "AbstractConvergenceChecker",
and also to remove the default (no-arg) constructor for all the convergence checkers defined
in CM, i.e.:
* AbstractConvergenceChecker
* SimpleValueChecker
* SimpleUnivariateValueChecker
* SimplePointChecker
* SimpleVectorValueChecker

In turn, this implies the removal of some of the constructors (which call the above constructors)
in the following classes:
* SimplexOptimizer
* BaseAbstractMultivariateOptimizer
* BaseAbstractMultivariateVectorOptimizer
* CMAESOptimizer
* BaseAbstractMultivariateSimpleBoundsOptimizer
* AbstractScalarDifferentiableOptimizer
* GaussNewtonOptimizer
* AbstractLeastSquaresOptimizer
* NonLinearConjugateGradientOptimizer
* LevenbergMarquardtOptimizer

To maintain backwards-compatibility, the fields and constructors will be deprecated but not
removed until the preparation of release 4.0.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message