Skip to content
Snippets Groups Projects
Commit a156f2b4 authored by MichelJuillard's avatar MichelJuillard
Browse files

Merge pull request #990 from JohannesPfeifer/mode_file

Delete mode-file option after completing estimation
parents e79968d5 08b42f9a
No related branches found
No related tags found
No related merge requests found
...@@ -4905,7 +4905,11 @@ simulation that crashed prematurely. Shouldn't be used together with ...@@ -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}
......
...@@ -199,3 +199,4 @@ if nnobs > 1 && horizon > 0 ...@@ -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)
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment