[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #38691] optim package conflicting with octave'
From: |
Muhali |
Subject: |
[Octave-bug-tracker] [bug #38691] optim package conflicting with octave's optimization |
Date: |
Wed, 10 Apr 2013 06:11:13 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 |
Follow-up Comment #2, bug #38691 (project octave):
the question is why in these lines
----
error: /usr/local/octave-dev/share/octave/3.7.2+/m/optimization/fminsearch.m
at line 159, column 41
error: /usr/local/octave-dev/share/octave/packages/optim-1.2.2/fmins.m at line
77, column 10
error: /usr/local/octave-dev/share/octave/packages/optim-1.2.2/fminsearch.m at
line 33, column 6
----
fminsearch is first taken from the package (3rd line) and then from octave
(1st line). Note the order is reversed in this error report. Or in other
words, why is fminsearch called a second time here (1st line)? line 77 of
fmins.m is
ret = feval(minfun, funfun, X0, stopit, [], varargin{:});
with
minfun = nmsmax
funfun = @sin
So why is fminsearch called here at all, and why is it not taken from the
package?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38691>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/