stepan
/
dynare
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #990 from JohannesPfeifer/mode_file 

Delete mode-file option after completing estimation
time-shift
MichelJuillard 2015-07-23 17:22:48 +02:00
parent e79968d5ad 08b42f9adb
commit a156f2b42c
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/dynare.texi
View File

@ -4905,7 +4905,11 @@ simulation that crashed prematurely. Shouldn't be used together with
Name of the file containing previous value for the mode. When Name of the file containing previous value for the mode. When
computing the mode, Dynare stores the mode (@code{xparam1}) and the computing the mode, Dynare stores the mode (@code{xparam1}) and the
hessian (@code{hh}, only if @code{cova_compute=1}) in a file called hessian (@code{hh}, only if @code{cova_compute=1}) in a file called
@file{@var{MODEL_FILENAME}_mode.mat} @file{@var{MODEL_FILENAME}_mode.mat}. After a successful run of the estimation
command, the @code{mode_file} will be disabled to prevent other function calls
from implicitly using an updated mode-file. Thus, if the mod-file contains subsequent
@code{estimation} commands, the @code{mode_file} option, if desired, needs to be
specified again.
@item mode_compute = @var{INTEGER} | @var{FUNCTION_NAME} @item mode_compute = @var{INTEGER} | @var{FUNCTION_NAME}
@anchor{mode_compute} @anchor{mode_compute}

1
matlab/dynare_estimation.m
View File

@ -199,3 +199,4 @@ if nnobs > 1 && horizon > 0
end end
end end
end end
options_.mode_file = ''; %delete stored mode-file so that it is not reaccessed in later calls (and in case it was only set by the recursive estimation)