[
https://issues.apache.org/jira/browse/MATH-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966822#action_12966822
]
Gilles commented on MATH-451:
-----------------------------
I've committed the above change in revision 1042151.
Luc,
I think that the API will be a little (c)leaner if we indeed remove from the
interface the {{solve}} methods that lack the "maxEval" parameter (as you
suggested in the ML). Users that want a simple call can always resort to the
method in class {{UnivariateRealSolverUtils}}. There, I've put the default
value at {{Integer.MAX_VALUE}} but maybe it's a bit too high ;).
Please, let me know your final word on this. In case of removal, I'll also take
care of deprecating in MATH_2_X.
> "solvers": Make the maximum number of evaluations a parameter of the "solve"
> methods
> ------------------------------------------------------------------------------------
>
> Key: MATH-451
> URL: https://issues.apache.org/jira/browse/MATH-451
> Project: Commons Math
> Issue Type: Improvement
> Reporter: Gilles
> Assignee: Gilles
> Priority: Minor
> Fix For: 3.0
>
>
> Currently, the number of allowed evaluations is set by the
> {{setMaxEvaluations}} method.
> In the ML, it was proposed to pass that parameter when calling the {{solve}}
> method. The setter will be removed.
> The existing {{solve}} methods will remain, using a default value (100) for
> the the maximum number of evaluations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
