#209: check use of set_default_option()
--------------------------+-------------------------------------------------
Reporter: michel | Owner:
Type: bug | Status: new
Priority: major | Milestone: 4.3
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
set_default_option takes an action only if the field name doesn't exist in
options_. But, now, most options have a default value set in
global_initialization.m, so most of the calls to set_default_option are
useless and may, sometimes, not produce the desired results.
--
Ticket URL: <https://www.dynare.org/trac/ticket/209>
Dynare <http://www.dynare.org>
The Dynare project
#160: Add derivatives of static model w.r.t. parameters
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner: sebastien
Type: enhancement | Status: new
Priority: minor | Milestone: 4.3
Component: Preprocessor | Version:
Keywords: |
--------------------------+-------------------------------------------------
Currently, the derivatives of the static model w.r.t. parameters are
computed using the derivatives of the dynamic model w.r.t. parameters.
It would be more convenient to provide directly these derivatives.
--
Ticket URL: <https://www.dynare.org/trac/ticket/160>
Dynare <http://www.dynare.org>
The Dynare project
#141: Replace strmatch which is a deprecated function in Matlab
--------------------------+-------------------------------------------------
Reporter: houtanb | Owner:
Type: bug | Status: new
Priority: major | Milestone:
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
Use strncmp instead, which has a different return type
http://www.mathworks.com/help/techdoc/ref/strmatch.html
--
Ticket URL: <https://www.dynare.org/trac/ticket/141>
Dynare <http://www.dynare.org>
The Dynare project
#230: Parallelize the testsuite
--------------------------------------+-------------------------------------
Reporter: sebastien | Owner: sebastien
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Build system / Packaging | Version:
Keywords: |
--------------------------------------+-------------------------------------
Currently the testsuite only uses one processor.
We should paralellize it, probably using the -j option of make.
Some tests have to be run in sequential order (the 2nd test depends on the
result of the 1st): those should probably lie in a separate list of tests
which will not be (fully) parallelized.
Need to think about a way to aggregate the tests results into one report.
--
Ticket URL: <https://www.dynare.org/trac/ticket/230>
Dynare <http://www.dynare.org>
The Dynare project
#222: Crash in estimation
---------------------------------+------------------------------------------
Reporter: sebastien | Owner: ferhat
Type: bug | Status: new
Priority: major | Milestone:
Component: Block decomposition | Version: 4.2.2
Keywords: |
---------------------------------+------------------------------------------
I attach the MOD file and data.
Reported on the forum:
http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=3402
--
Ticket URL: <https://www.dynare.org/trac/ticket/222>
Dynare <http://www.dynare.org>
The Dynare project
#35: Putting "shocks" before "endval" leads to wrong results
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner:
Type: bug | Status: new
Priority: major | Milestone: 4.1
Component: Core M-files | Version: 4.0.4
Keywords: |
--------------------------+-------------------------------------------------
In a deterministic setup with both temporary and permanent shocks, the
order of the {{{shocks}}} and {{{endval}}} blocks matter. Actually,
putting {{{shocks}}} before {{{endval}}} leads to wrong results.
{{{shocks}}} uses {{{set_shocks.m}}}, which fills in {{{oo_.exo_simul}}};
the point is that, if {{{endval}}} has not been used, this structure is
empty, so {{{set_shocks}}} fills it, at date of shocks, for ''all'' the
exogenous, and using the ''initial'' steady state value.
When {{{simul}}} is finally called, it completes {{{oo_.exo_simul}}} with
the ''final'' exogenous steady state, but only for those periods which
have no temporary shocks. So at the dates with temporary shocks, the value
of exogenous which are permanently shocked is wrong.
A quick fix is to forbid the use of {{{shocks}}} before {{{endval}}}.
A cleaner fix is to modify {{{set_shocks.m}}} so that it only sets values
for the exogenous which are temporarily shocked, and leaves {{{NaN}}} for
other exogenous. It would be {{{simul}}}'s job to fill in the holes.
--
Ticket URL: <https://www.dynare.org/trac/ticket/35>
Dynare <http://www.dynare.org>
The Dynare project
#102: forecast graphs in manual
---------------------------+------------------------------------------------
Reporter: michel | Owner: michel
Type: bug | Status: new
Priority: minor | Milestone:
Component: Documentation | Version:
Keywords: |
---------------------------+------------------------------------------------
The graphs of forecasts with uncertainty about the parameters have changed
but we didn't modify the user manual and the user guide
--
Ticket URL: <https://www.dynare.org/trac/ticket/102>
Dynare <http://www.dynare.org>
The Dynare project