[Octave-bug-tracker] [bug #64516] optimset silently replace user defined "n" with "niter_check_tolfun"

[Dmitri A. Sergatskov]

Follow-up Comment #2, bug #64516 (project octave):

What version of octave do you use?
What does "which optimset" return on your computer?
On my computer I see:

>> which optimset
'optimset' is a function from the file
/app/share/octave/8.2.0/m/optimization/optimset.m
>> options=optimset('n', 100)
warning: optimset: unrecognized option: n
warning: called from
    optimset>setoptionfields at line 187 column 9
    optimset at line 169 column 12

options =

  scalar structure containing the fields:

    n = 100


In any case optimset does case-insensitive autocopletion, e.g.:


>> options=optimset('j', 'on')
options =

  scalar structure containing the fields:

    Jacobian = on


but "niter_check_tolfun" is not a valid option.

Dmitri.
-- 






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64516>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/