cdrnet wrote:
Unfortunately you can't influence it from user code, but I've increased it to 120 in master and plan a new alpha release in a few days.I built the library locally with MaxIterations = 120; I still got the same problem for BetaRegularized with a = 0.038459322032068435; b = 2616.5472749092005; x = 0.00040236338211950594. (This was not a fringe test case, but an actual data set used in a simulation.) The result it would have returned after 120 iterations was close enough to the one we would have gotten after 201 iterations, which was the necessary iteration count for this data triple. So I don't think setting MaxIterations to 120 solves the problem for good. I suggest that instead:
- either a result is always returned
- or the MaxIterations is an input parameter
-
or there is an option to either throw an exception, or return a result in any case.