- Feb 05, 2019
-
-
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 Dynare/dynare!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 Dynare/dynare!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
-
Sébastien Villemot authored
Previously it was plain TeX. This allows us to remove the test for pdfetex.
-
Sébastien Villemot authored
By the way, simplify Makefile rules.
-
- Jan 30, 2019
-
-
Sébastien Villemot authored
The material of this document comes from the introduction to the library that had been lost in the move away from CWEB (formerly tl/cc/main.web). This file gives a good overview of the library. It has been adapted from TeX to LaTeX. Also I fixed a mistake in the Faà di Bruno's tensor formula.
-
- Jan 29, 2019
-
-
Sébastien Villemot authored
Forgotten in commit 73330880.
-
Sébastien Villemot authored
The former default was 2 threads, since Dynare++ was written at a time when hyper-threading was being generalized (but multiple cores were not).
-
Sébastien Villemot authored
-
- Jan 28, 2019
-
-
Sébastien Villemot authored
On Windows, this means that a POSIX threads implementation is no longer needed, since C++11 threads are implemented using native Windows threads. On GNU/Linux and macOS, POSIX threads are still used under the hood. A new m4 macro (AX_CXX11_THREAD) is used to add the proper compilation flags (instead of AX_PTHREAD).
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Houtan Bastani authored
-
Sébastien Villemot authored
-
Houtan Bastani authored
-
Stéphane Adjemian authored
Update dynare.texi See merge request Dynare/dynare!1642
-