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

[Olaf Till]

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

Checking also for Inf may be Matlab compatible, but I'm not sure we should
duplicate this behavior without good reason. A returned NaN can never be used
by the algorithm, but an algorithm might correctly interpret a returned Inf as
an increase of the value of the objective function. So checking for NaN or Inf
seem to be differently motivated and should not necessarily be turned on by
the same option.

And I would not see a need to include the "assert" line to check for the bug,
since the bug was simply a random typo. Of course you can include the "error"
line to check for FunValCheck catching complex values, but thats a different
thing. I simply wanted to correct the typos.

Olaf

    _______________________________________________________

Reply to this item at:

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

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