forcst function in Metropolis

This forum is closed. You can read the posts but cannot write. We have migrated the forum to a new location where you will have to reset your password.
Forum rules
This forum is closed. You can read the posts but cannot write. We have migrated the forum to a new location (https://forum.dynare.org) where you will have to reset your password.

forcst function in Metropolis

Postby azj » Mon Mar 06, 2006 8:52 pm

I noticed that in 3_064, each call to the forcst2 function in metropolis.m asks for only one forecast. ie:

yf1 = forcst2(yyyy,horizon,dr_,1);

In previous versions, the last argument passed to forcst2 was "B" (which at the time was set to 100, currently 500) instead of 1. Is there a reason that this version uses only 1 draw of the future shocks to determine the forecast uncertainty from the parameters and the future shocks?

Thanks,
Ariel
azj
 
Posts: 3
Joined: Mon Feb 27, 2006 7:19 pm

Postby MichelJuillard » Mon Mar 06, 2006 9:20 pm

Yes, this call takes place in a loop over B draws among metropolis iterations.

At first, I thought it was necessary to sample more for parameter uncertainty and intrinsic shocks, then I revised this opinion. I don't think anymore it is necessary to do B draws to describe parameter uncertainty and B*B draws for parameter uncertainty and intrinsic shocks

Of course, we should make B a parameter that users can tune. But as you have found it, you can now tune it by hand :)

Best

Michel
MichelJuillard
 
Posts: 680
Joined: Thu Nov 18, 2004 10:51 am


Return to Dynare help

Who is online

Users browsing this forum: Google [Bot] and 10 guests