[
https://issues.apache.org/jira/browse/MATH-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084454#comment-13084454
]
Dennis Hendriks commented on MATH-631:
--------------------------------------
bq. contains everything
I agree. I was just wondering why a message that seems to be exactly the same
as the exception was not used, as it kind of looked like it was created just
for this purpose...
bq. I proposed to use this approach (combining message items with the
"addMessage" method of "ExceptionContext") in order to reduce the number of
messages in the "LocalizedFormats" enum. Too many of them are just slight
variations on a same theme.
Ah, so then the MAX_EVALUATIONS_EXCEEDED is just a remnant of the past that
should be eliminated, by replacing it everywhere by the more general
MAX_COUNT_EXCEEDED?
> "RegulaFalsiSolver" failure
> ---------------------------
>
> Key: MATH-631
> URL: https://issues.apache.org/jira/browse/MATH-631
> Project: Commons Math
> Issue Type: Bug
> Reporter: Gilles
> Fix For: 3.0
>
>
> The following unit test:
> {code}
> @Test
> public void testBug() {
> final UnivariateRealFunction f = new UnivariateRealFunction() {
> @Override
> public double value(double x) {
> return Math.exp(x) - Math.pow(Math.PI, 3.0);
> }
> };
> UnivariateRealSolver solver = new RegulaFalsiSolver();
> double root = solver.solve(100, f, 1, 10);
> }
> {code}
> fails with
> {noformat}
> illegal state: maximal count (100) exceeded: evaluations
> {noformat}
> Using "PegasusSolver", the answer is found after 17 evaluations.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
