From 1084a2d452a7f218c5ef43551a71957a56359c08 Mon Sep 17 00:00:00 2001
From: Johannes Pfeifer <jpfeifer@gmx.de>
Date: Tue, 14 Jun 2016 15:18:05 +0200
Subject: [PATCH] Document new behavior of mh_recover and mh_replic
---
doc/dynare.texi | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/doc/dynare.texi b/doc/dynare.texi
index 6a938c3df2..a2ace0642e 100644
--- a/doc/dynare.texi
+++ b/doc/dynare.texi
@@ -5124,8 +5124,9 @@ Metropolis-Hastings chain. Default: 2*@code{mh_scale}
@anchor{mh_recover} Attempts to recover a Metropolis-Hastings
simulation that crashed prematurely, starting with the last available saved
@code{mh}-file. Shouldn't be used together with
-@code{load_mh_file} or a different @code{mh_replic} than in the crashed run.
-To assure a neat continuation of the chain with the same proposal density, you should
+@code{load_mh_file} or a different @code{mh_replic} than in the crashed run. Since Dynare 4.5
+the proposal density from the previous run will automatically be loaded. In older versions,
+to assure a neat continuation of the chain with the same proposal density, you should
provide the @code{mode_file} used in the previous
run or the same user-defined @code{mcmc_jumping_covariance} when using this option.
@@ -5293,7 +5294,12 @@ when finite values are required for computational reasons. Default: @code{1e7}
@item load_mh_file
@anchor{load_mh_file} Tells Dynare to add to previous
Metropolis-Hastings simulations instead of starting from
-scratch. Shouldn't be used together with @code{mh_recover}
+scratch. Since Dynare 4.5
+the proposal density from the previous run will automatically be loaded. In older versions,
+to assure a neat continuation of the chain with the same proposal density, you should
+provide the @code{mode_file} used in the previous
+run or the same user-defined @code{mcmc_jumping_covariance} when using this option.
+Shouldn't be used together with @code{mh_recover}.
@item optim = (@var{NAME}, @var{VALUE}, ...)
@anchor{optim}
--
GitLab