[Octave-bug-tracker] [bug #45871] fsolve. different output octave and matlab

[anonymous]

Follow-up Comment #3, bug #45871 (project octave):

Hello John. Thanks for replying. Yes, dynare is needed. The whole problem was
to solve a steady state model, which can only be done with dynare, with the
help of the fsolve() function. But I just found what was wrong. It's in the
options. Probably the default value of matlab is bigger than octave...the
problem is that octave was stopping before finding the optimal value. 

The code changed from :
options=optimset('Display','iter','MaxFunEvals',200000,'TolFun',1e-8);  (in
the mod_fiscal_04_ss_solve.m)

To 

options=optimset('Display','iter','MaxFunEvals',200000,'TolFun',1e-8,'MaxIter',1000);
 

I don't know if I was completely clear. If not, just rewrite so I can explain
it better.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45871>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/