Hi,
I don’t see the point of this. The preprocessor sets
M_.params( 11 ) = M_.params(2);
optimal_policy_discount_factor = M_.params( 11 );
But then the variable optimal_policy_discount_factor in the workspace is never used again. Rather, we always use get_optimal_policy_discount_factor.m to retrieve the value directly from M_.params. Can’t we just drop assigning this variable?
Best,
Johannes
Von: Dev [mailto:dev-bounces@dynare.org] Im Auftrag von Houtan
Gesendet: Montag, 31. August 2015 15:16
An: List for Dynare developers
Betreff: Re: [DynareDev] Preprocessor discretionary_policy
The problem is precisely because there are two discretionary_policy statements. The preprocessor creates a parameter called optimal_policy_discount_factor from the planner_discount option or, if it doesn’t exist, declares it and sets it equal to 1. As parameter and variable names are unique, when the preprocessor encounters the second discretionary_policy statement with the planner_discount option, it breaks because it tries to declare a parameter with a name that is already taken. If you remove this second option, you will see that it will run all the way through, using the discount_factor declared in the first statement.
If we do indeed want to support multiple discretionary_policy, ramsey_model, and ramsey_policy statements in a .mod file, we will need to think of a slight hack (perhaps storing the value of planner-discount in the statement options and overwriting the optimal_policy_discount_factor parameter with this value when before calling discretionary_policy and the like (ramsey_model, ramsey_policy).
Best,
Houtan