[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
## Re: Trouble with fsolve

**From**: |
Joel Konkle-Parker |

**Subject**: |
Re: Trouble with fsolve |

**Date**: |
Wed, 19 Oct 2005 07:19:19 -0500 |

On Tue, 2005-10-18 at 17:17 +0200, David Bateman wrote:
>* together with the explanation of why this is the wrong way to go.. Note *
>* that the changes to "quad" were made. However daspk, dasrt, dassl, *
>* fsolve, lsode and odessa weren't converted as the resulting code is an *
>* ugly hack. The only real solution is to completely dump the existing *
>* mess for these functions and reimplement it removing the underlying *
>* fortran code.... So a workaround with global variables is the only way *
>* this can be done at the moment in octave..*
Have you guys looked at SciPy for an example? Their fsolve function lets
you include multiple parameters, and according to them, it's just a
simple wrapper around MINPACK.
http://www.scipy.org/documentation/apidocs/scipy/scipy.optimize.minpack.html#-fsolve
--
Joel Konkle-Parker
-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
Octave's home on the web: http://www.octave.org
How to fund new projects: http://www.octave.org/funding.html
Subscription information: http://www.octave.org/archive.html
-------------------------------------------------------------