From ebe69b7cea9c84d790bf85993a0ad5f4ca6c63d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Villemot?= Date: Thu, 2 Dec 2010 17:43:46 +0100 Subject: [PATCH] Reference manual: give the status of the various optimization routines under Octave --- doc/manual.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/manual.xml b/doc/manual.xml index ebb2eebbb..36f702337 100644 --- a/doc/manual.xml +++ b/doc/manual.xml @@ -3247,13 +3247,13 @@ end; Specifies the optimizer for the mode computation: 0: the mode isn't computed. option must be specified - 1: uses MATLAB's fmincon + 1: uses fmincon optimization routine (not available under Octave) 2: value no longer used - 3: uses MATLAB's fminunc + 3: uses fminunc optimization routine 4: uses Chris Sims's csminwel 5: uses Marco Ratto's newrat 6: uses a Monte-Carlo based optimization routine (see Dynare wiki for more details) - 7: uses MATLAB's fminsearch (a simplex based routine) + 7: uses fminsearch, a simplex based optimization routine (available under Octave if the optim package from Octave-Forge is installed) It is also possible to give a FUNCTION_NAME to this option, instead of an INTEGER. In that case, Dynare takes the return value of that function as the posterior mode.