[
https://issues.apache.org/jira/browse/MATH-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854071#action_12854071
]
Roman Werpachowski edited comment on MATH-362 at 4/6/10 5:22 PM:
-----------------------------------------------------------------
I would keep using orthoTolerance as it is used now:
{quote}
292 if (maxCosine <= orthoTolerance) \{
293 // convergence has been reached
294 return new VectorialPointValuePair(point, objective);
295 \}
{quote}
and then use costRelativeTolerance & parRelativeTolerance if and only if the
convergence checker is null, otherwise use the convergence checker and ignore
{costRelativeTolerance, parRelativeTolerance}.
What I am missing now is the ability to bail out if the absolute distance from
the target falls below some value ("close enough").
was (Author: roman.werpachowski):
I would keep using orthoTolerance as it is used now:
292 if (maxCosine <= orthoTolerance) {
293 // convergence has been reached
294 return new VectorialPointValuePair(point, objective);
295 }
and then use costRelativeTolerance & parRelativeTolerance if and only if the
convergence checker is null, otherwise use the convergence checker and ignore
{costRelativeTolerance, parRelativeTolerance}.
What I am missing now is the ability to bail out if the absolute distance from
the target falls below some value ("close enough").
> LevenbergMarquardtOptimizer ignores the VectorialConvergenceChecker parameter
> passed to it
> ------------------------------------------------------------------------------------------
>
> Key: MATH-362
> URL: https://issues.apache.org/jira/browse/MATH-362
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Roman Werpachowski
>
> LevenbergMarquardtOptimizer ignores the VectorialConvergenceChecker parameter
> passed to it. This makes it hard to specify custom stopping criteria for the
> optimizer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
