> > public void testSolveBadAccuracy() throws MathException {
> > try { // bad accuracy
> > UnivariateRealSolverUtils.solve(sin, 0.0, 4.0, 0.0);
>
> I guess this one cannot be triggered anymore since changes to
> convergence behavior. The ConvergingAlgorithm that provides the
> setAbsoluteAccuracy method is now deprecated in 2.2, should be removed
> in 3.0 but is still there, and doesn't check the accuracy is positive.
>
> I guess it's a work in progress.
I didn't touch the classes in package "analysis.solvers" yet (as part of
reworking on the convergence settings). Could it be that the problem is
ancient but was somehow hidden by the way the test were done?
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
