Commits on Source (64)
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
Uses: – structured bindings – std::map::contains and std::map::at – std::boolalpha and std::noboolalpha
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Stéphane Adjemian authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
– New “heterogeneity_dimension” statement – New option “heterogeneity” to “var”, “varexo”, “parameters”, “model” and “shocks” statements – New “SUM()” operator in “model” block
-
Sébastien Villemot authored
The driver was calling “clear” before “global”, hence clearing local and not global variables (unless “global” had already been called at scope). Rather use “clearvars -global”.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
This rule is obviously incorrect (and useless): – it begins with an unescaped dollar sign, which can only match an end-of-line (so it makes no sense to have it at the beginning of the rule) – it prints to standard output, which is obviously not the intended action
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Normann Rion authored
HANK support: modifies the driver file writing process to introduce a `state_var` field in the `M_.heterogeneity(i)` structure for each heterogeneity dimension `i`
-
Sébastien Villemot authored
HANK support: modifies the driver file writing process to introduce a... See merge request Dynare/preprocessor!108
-
Sébastien Villemot authored
Epilogue variables can have leads/lags when appearing on the RHS of the epilogue block. The method VariableNode::maxLagWithDiffsExpanded() was already handling them, so this commit adapts other methods for consistency.
-
Sébastien Villemot authored
This should have been removed in commit 2315bdb5. Ref. dynare#1859
-
Sébastien Villemot authored
Field names used in the option structure were slightly different depending on whether the option value was an integer or a date. This is confusing. This commit aligns the structure field names with the option names. Type checking can then be done at the MATLAB/Octave level.
-
Sébastien Villemot authored
This information can be computed from MATLAB/Octave. This will facilitate the introduction of dates in shock sequences.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
The call to model_error() would return and lead to an incorrect dereferencing of the optional<int> rv. The call to model_error() should have been replaced by a call to error() in db1f6c29. Then the move to an optional<int> in 46b2c735 introduced the bug. See https://forum.dynare.org/t/preprocessing-failed-for-specific-mod-file/26705
-
Sébastien Villemot authored
Also do some coding style manual enforcement.
-
Sébastien Villemot authored
– Harmonize location output for warnings so that it is the same as for errors (i.e. more explicit about what is the line number and the column number) – Remove obsolete stuff for delayed error messages that should have been removed in db1f6c29. – Factorize some printing logic with ParsingDriver::undeclared_model_variable_error(). – Simplify WarningConsolidation class
-
Sébastien Villemot authored
Dates handling inside Dynare statements was done in the Flex scanner using a hack that would introduce some extra characters in the character stream (in order to return a call to the “dates('…')” constructor to Bison). But this would break the column location counter, because the latter would count characters that do not exist in the user file. This commit fixes it by implementing a more natural handling of dates, adding the “dates('…')” constructor directly at the level of the semantic value.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
[skip ci]
-
Sébastien Villemot authored
-
Sébastien Villemot authored
– enable new options InsertNewlineAtEOF and RemoveSemicolon – reformat the code accordingly
-
Sébastien Villemot authored
-
Sébastien Villemot authored
Automatically detected using clang-tidy with modernize-use-nodiscard check.
-
Sébastien Villemot authored
Automatically detected by clang-tidy using modernize-use-equals-default check.
-
Johannes Pfeifer authored
-
Sébastien Villemot authored
Allow non_zero option in steady command See merge request !109
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
New options {first,last}_simulation_period to perfect_foresight{,with_expectation_errors}_setup commands
-
Sébastien Villemot authored
-
Sébastien Villemot authored
NB: the “overwrite” option only works for the same type of “learnt_in” value, i.e. an integer-valued “learnt_in” cannot replace a date-valued “learnt_in” and vice versa.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
The regression was introduced in commit 84d792bc, when leads/lags were allowed on model-local variables. The treatment of model-local variables without leads/lags was negatively impacted. This commit fixes the regression by restoring the former behaviour for model-local variables without leads/lags. Reported on https://forum.dynare.org/t/pre-processing-takes-very-long/26865 Ref. dynare#1929
-
Sébastien Villemot authored
-
Sébastien Villemot authored
However do not set that option permanently (and also disable RemoveSemicolon by default), since the clang-format manual states that these options can lead to incorrect formatting and thus their result should be carefully reviewed.
-
Sébastien Villemot authored
-
Stéphane Adjemian authored
Use simulation of the model, based on a first order approximation, as an initial guess for the solver in each period.
-
Sébastien Villemot authored
Ref. dynare#1949
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Sébastien Villemot authored
Implement the fix that is already present in assignment operator (in particular for dynare#1782).
-
Sébastien Villemot authored
By the way, also improve the check for when the pac_expectation is used two times on the same model.
-
Stéphane Adjemian authored
-
Stéphane Adjemian authored
-
Sébastien Villemot authored
Commit 8c021084 had removed the possibility of using “residual” as a variable name. In particular, this broke the lmmcp/rbc.mod test.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
Ref. dynare#1960
Showing
- .clang-format 3 additions, 0 deletions.clang-format
- .gitlab-ci.yml 14 additions, 1 deletion.gitlab-ci.yml
- scripts/wasm.ini 44 additions, 0 deletionsscripts/wasm.ini
- src/CommonEnums.hh 21 additions, 10 deletionssrc/CommonEnums.hh
- src/ComputingTasks.cc 8 additions, 13 deletionssrc/ComputingTasks.cc
- src/ComputingTasks.hh 5 additions, 5 deletionssrc/ComputingTasks.hh
- src/Configuration.cc 26 additions, 43 deletionssrc/Configuration.cc
- src/Configuration.hh 1 addition, 1 deletionsrc/Configuration.hh
- src/DataTree.cc 29 additions, 17 deletionssrc/DataTree.cc
- src/DataTree.hh 16 additions, 3 deletionssrc/DataTree.hh
- src/DynamicModel.cc 65 additions, 48 deletionssrc/DynamicModel.cc
- src/DynamicModel.hh 8 additions, 2 deletionssrc/DynamicModel.hh
- src/DynareBison.yy 170 additions, 92 deletionssrc/DynareBison.yy
- src/DynareFlex.ll 74 additions, 114 deletionssrc/DynareFlex.ll
- src/ExprNode.cc 271 additions, 67 deletionssrc/ExprNode.cc
- src/ExprNode.hh 41 additions, 20 deletionssrc/ExprNode.hh
- src/HeterogeneityTable.cc 139 additions, 0 deletionssrc/HeterogeneityTable.cc
- src/HeterogeneityTable.hh 100 additions, 0 deletionssrc/HeterogeneityTable.hh
- src/HeterogeneousModel.cc 239 additions, 0 deletionssrc/HeterogeneousModel.cc
- src/HeterogeneousModel.hh 101 additions, 0 deletionssrc/HeterogeneousModel.hh
scripts/wasm.ini
0 → 100644
This diff is collapsed.
This diff is collapsed.
src/HeterogeneityTable.cc
0 → 100644
src/HeterogeneityTable.hh
0 → 100644
src/HeterogeneousModel.cc
0 → 100644
src/HeterogeneousModel.hh
0 → 100644