[Octave-bug-tracker] [bug #64525] optimset/optimget issues warning, rather than error, when short name matches multiple possible options

[Nicholas Jankowski]

Update of bug #64525 (project octave):

                  Status:                   Fixed => Confirmed              
             Open/Closed:                  Closed => Open                   

    _______________________________________________________

Follow-up Comment #3:

looks like optimget returns an empty array unless something with the actual
ambiguous name is present. since it's currently valid to set arbitrary fields,
an error being issued might prevent querying a manually set parameter with
optimget:


>> a = optimset('max_fract_change',1, 'max_rand_step',2, 'MaxFunEvals',3,
'MaxIter',4)
a =

  scalar structure containing the fields:

    max_fract_change = 1
    max_rand_step = 2
    MaxFunEvals = 3
    MaxIter = 4

>> optimget(a, 'max')
warning: optimget: ambiguous option: max (max_fract_change, max_rand_step,
MaxFunEvals, MaxIter)
warning: called from
    optimget at line 55 column 5

ans = [](0x0)

>> a.max = 6
a =

  scalar structure containing the fields:

    max_fract_change = 1
    max_rand_step = 2
    MaxFunEvals = 3
    MaxIter = 4
    max = 6

>> optimget(a, 'max')
warning: optimget: ambiguous option: max (max_fract_change, max_rand_step,
MaxFunEvals, MaxIter)
warning: called from
    optimget at line 55 column 5

ans = 6




    _______________________________________________________

Reply to this item at:

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

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