Re: bfgsmin

[Michael Creel]

Bertrand Roessli wrote:
> 
> Sorry I do not get it,
> 
> "Just download that file to your working directory," 
> 
> which file? 
> 
> If you mean from optim-1.04, it is what I did before.
> 
> Bertrand
> 
> On Mon, 2009-03-16 at 07:00 -0700, Michael Creel wrote:
>> 
>> Bertrand Roessli wrote:
>> > 
>> > Hello,
>> > 
>> > Thanks for trying the code. 
>> > 
>> > I have the latest package from octave sourceforge (optim 1.04) and
>> > octave 3.1.54.
>> > 
>> > 
>> 
>> It seems that the optim package was last released in August of 2008,
>> while
>> the last change to __bfgsmin.cc was in October 2008. I just ran your code
>> 10
>> times without problems, so I think that the problem is a bug in the old
>> version of __bfgsmin.cc. Just download that file to your working
>> directory,
>> run mkoctfile __bfgsmin.cc, and I think you'll be set.
>> Michael
>> 
>> p.s., I have not tested it with Octave 3.1.x, 
>> 
> 
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
> 
> 

You can browse the SVN repository to get individual files. __bfgsmin.cc is
here:
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/optim/src/__bfgsmin.cc?view=log

Just click on that, then download the latest version. You can browse around
the SNV repo to see the stucture, if you're curious. Because __bfgsmin.cc is
written in C++, it needs to be compiled before it can be used by Octave.
That's why you need the mkoctfile step I mentioned before.
Cheers, Michael

-- 
View this message in context: 
http://www.nabble.com/Nonlinear-fitting-with-lg%28a%2Bx%29-tp22492005p22541400.html
Sent from the Octave - General mailing list archive at Nabble.com.