 17 Aug, 2018 1 commit


Houtan Bastani authored

 16 Aug, 2018 1 commit


Houtan Bastani authored

 14 Aug, 2018 2 commits


Stéphane Adjemian(Charybdis) authored

Stéphane Adjemian(Charybdis) authored

 13 Aug, 2018 5 commits


Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

 09 Aug, 2018 1 commit


Houtan Bastani authored

 08 Aug, 2018 7 commits


Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

 07 Aug, 2018 3 commits


Houtan Bastani authored

Houtan Bastani authored

Houtan Bastani authored

 06 Aug, 2018 1 commit


Stéphane Adjemian(Charybdis) authored

 04 Aug, 2018 3 commits


Stéphane Adjemian(Charybdis) authored

Stéphane Adjemian(Charybdis) authored

Stéphane Adjemian(Charybdis) authored

 02 Aug, 2018 1 commit


Sébastien Villemot authored
Given a previously declared var_model, the var_expectation_model statement is used to declare a way of forming expectations with this VAR (possibly using a finite or infinite discounted sum). The var_expectation operator now takes a single argument, the name of the var_expectation_model. For the moment, this only works when the var_model is using equations explicitly declared in the model block.

 01 Aug, 2018 1 commit


Sébastien Villemot authored

 31 Jul, 2018 7 commits


Sébastien Villemot authored
By the way, error out if the planner_objective statement is used two times.

Sébastien Villemot authored

Sébastien Villemot authored

Sébastien Villemot authored

Sébastien Villemot authored

Sébastien Villemot authored
We can therefore manipulate objects by value rather than by pointers, which saves a lot of memory manipulations (and avoid potential segfaults and memory leaks). Note that there is no default action ("$$ = $1") when using the variant type, so we add them explicitly.

Sébastien Villemot authored
 store objects whose persistence is not guaranteed (e.g. strings) as values instead of references (to avoid possible segfaults)  on the contrary, always store the SymbolTable as a reference, since its persistence is guaranteed, and we don't want to copy it  use passbyvalue in constructors whenever possible  remove useless const keyword when passing by value

 30 Jul, 2018 2 commits


Sébastien Villemot authored

Sébastien Villemot authored
See McModelTeam/McModelProject/issues/97.

 27 Jul, 2018 1 commit


Sébastien Villemot authored
aux_equations only contain the definition of auxiliary variables, and may diverge from those in the main model (equations), if other model transformations applied subsequently. This is not a problem, since aux_equations is only used for regenerating the values of auxiliaries given the others. For example, such a divergence appears when there is an expectation operator in a ramsey model, see tests/optimal_policy/nk_ramsey_expectation.mod */

 26 Jul, 2018 2 commits


Sébastien Villemot authored
This table serves no useful purpose. It is better to append auxiliary equations at the time they are created, to avoid messing with the recursive ordering.

Sébastien Villemot authored
Ensure that all diff operators appear once with their argument at current period (i.e. maxLag=0). If it is not the case, generate the corresponding expressions. This is necessary to avoid lags of more than one in the auxiliary equation, which would then be modified by subsequent transformations (removing lags > 1), which in turn would break the recursive ordering of auxiliary equations. See McModelTeam/McModelProject/issues/95 for an example.

 25 Jul, 2018 2 commits


Sébastien Villemot authored
This is now easy to implement, thanks to the refactoring allowing any type of objects in arrays. Closes DynareTeam/dynare#707

Sébastien Villemot authored
Closes DynareTeam/Dynare#1547
