[Octave-bug-tracker] [bug #35534] fminunc: FunValCheck buggy

[Olaf Till]

Follow-up Comment #5, bug #35534 (project octave):

I didn't speak of reversing the search direction. Consider a search direction
in which the function value first decreases and then increases until it gets
too high (gets Inf). Algorithms sometimes test step-widths while not (much)
changing search direction. If the first step width is too high it might
produce an Inf value. The algorithm can then shorten the step width until it
gets a function value less than current. The previous Inf value might be just
due to the limits of floating point representation and not a programming
error. A NaN value indicates a problem of a different kind.

But if you disagree, why don't you just make the change you propose? This
problem is separate from my typo patch. The same applies for the tests.

As for the tests, my objection came from the fact that you explicitly named it
a test for bug 35534 first, not a general test.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?35534>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/