- Feb 09, 2019
-
-
Stéphane Adjemian authored
-
- Feb 07, 2019
-
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
- Feb 06, 2019
-
-
Sébastien Villemot authored
Similarly to Vector, it now uses a std::shared_ptr for managing the underlying data.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
Stéphane Adjemian authored
-
Stéphane Adjemian authored
M_.endo_names and M_.exo_names are cell arrays, no need to use deblank to remove trailing whitespaces.
-
- Feb 05, 2019
-
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Sébastien Villemot authored
Since the introduction of the --burn option (in Dynare++ shipped with Dynare 4.3.0), the IRFs reported by Dynare++ were wrong. The IRFs are computed using a generalized IRF method: the result is the (average) difference between a simulation with shock and a simulation without shock. The problem was that the two simulations were not using the same starting point. Closes #1634
-
Sébastien Villemot authored
discretionary_policy_1.m: check for NaN before checking for non-zero derivatives See merge request !1644
-
Sébastien Villemot authored
mr_hessian.m: prevent infinite loop Closes #1636 See merge request Dynare/dynare!1645
-
Sébastien Villemot authored
Document treatment of several Matlab statements in one line See merge request !1646
-
Johannes Pfeifer authored
Related to #1637
-
Johannes Pfeifer authored
Make sure hessian is not 0 and add counter. Fixes #1636
-
Johannes Pfeifer authored
Prevents false error message
-
- Feb 04, 2019
-
-
Stéphane Adjemian authored
[skip ci]
-
Stéphane Adjemian authored
Fixes 4.6 See merge request Dynare/dynare!1641
-
Stéphane Adjemian authored
- Only works with backward models. - Probably doesn't work if the model includes auxiliary variables. - Assumes that the trends are multiplicative.
-
Stéphane Adjemian authored
-
- Feb 02, 2019
-
-
Sébastien Villemot authored
At the end of a thread, we must first notify the main thread waiting on the condition variable, then unlock the mutex. We must do these two operations in that order, otherwise there is a possibility of having the main process destroying the condition variable before the thread tries to notify it (if all other threads terminate at the same time and bring the counter down to zero). For that reason, we cannot use std::notify_all_at_thread_exit(). Bug introduced in commit 752a02a3.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
-
- Feb 01, 2019
-
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Sumudu Kankanamge authored
-
Sébastien Villemot authored
GCC 5 supports C++14, but it is still not enough because it does not implement N4387 that was retroactively applied to the standard in 2015 (see the "Notes" and "Defect reports" sections of https://en.cppreference.com/w/cpp/utility/tuple/tuple).
-
- Jan 31, 2019
-
-
Sébastien Villemot authored
Another version is already under tests/trend_var/ directory.
-
Sébastien Villemot authored
-
Sébastien Villemot authored
Also fix extensions of source files.
-
Sébastien Villemot authored
-
Houtan Bastani authored
-