Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
dynare
dynare
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 121
    • Issues 121
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Dynare
  • dynaredynare
  • Wiki
  • Known bugs present in the current stable version

Last edited by Johannes Pfeifer Jan 23, 2021
Page history

Known bugs present in the current stable version

This page documents known bugs in Dynare stable.

  • Passing multiple shock values through a MATLAB/Octave vector in a mshocks block does not work (bug fixed in ffa828a6 and 12ef7531)
  • mode_compute=12 is broken (bug fixed via !1784)
  • The use_mh_covariance was ignored (bug not yet fixed, see cef13ffd)
  • The use_mh_covariance does not work with mh_tune_jscale (bug not yet fixed, see 0090de63)
  • The forecast-option is ignored when using mode_compute=0 without a mode-file to execute the smoother (bug fixed, see !1802)
  • discretionary_policy crashes in the presence of news shocks (bug fixed via !1767)
  • ramsey_constraints crashes if the constraint contains defined parameters (bug fixed in !1788)
  • Identification will display a wrong error message if a unit root is present and diffuse_filter has been set (bug fixed via !1782)
  • particle filter estimation will crash if the initial state covariance becomes singular for a draw (bug fixed via 38e300b9)
  • particle filter estimation will crash if k_order_solver is specified with options_.particle.pruning (bug fixed via 0b87f664)
  • The initial state covariance in particle filter estimation may be NaN when using nonlinear_filter_initialization=2 despite options_.particles.pruning=1 (bug fixed in f19decf2)
  • Output of smoother-results when using particle filters will be based on order=1 (bug fixed, in 417f038c)
  • Output of moments_varendo-results when using particle filters will be based on order=1 (bug fixed in dedfd0c0, 314948ce. and b38d6f81)
  • When decreasing the order in mod-files, oo_.dr may contain stale results from higher orders (bug not yet fixed, see #1767)
  • Estimation results using the particle filter at order=3 will be incorrect if the restricted state space differs from the unrestricted one (bug not yet fixed, see #1768)
  • mode_compute=102 (SOLVEOPT) may return with Inf instead of the last feasible value (bug fixed in a89f21b5)
  • Using analytic_derivation for Bayesian estimation will result in wrong results when the multivariate Kalman filter enters the steady state stage (bug fixed in c6c9b4e3)
  • Using analytic_derivation for ML estimation will result in a crash (bug fixed in 82aa669b)
  • cova_compute=0 did not work with user-defined MCMC_jumping_covariance (bug fixed via 9351fd66)
  • mode_compute=1 does not work with analytic_derivation (bug not yet fixed, see #1770)
  • Not all commands honor saving to the M_.dname-folder (bug fixed, see da3943be)
  • LaTeX output of the simulated variance decomposition for observables with measurement error may have a wrong variable label (bug fixed in f721a14f)
  • Forecasts are only based on the DSGE-model, not the DSGE-VAR (bug not yet fixed; see #819)
  • smoother2histval will crash if variable names are too similar (bug fixed, see !1800)
  • smoother2histval does not keep track of whether previously stored results were generate with loglinear (bug not yet fixed; see #1407)
  • The initval_file option does not yet support Dynare's translation of a model into a one lead/lag-model via auxiliary variables (bug not yet fixed; see #1004)

Clone repository
  • Auxiliary variables
  • BreakingFeaturesIn4.6
  • DSGE VAR model
  • External function
  • FixedBugs
  • Home
  • Install on MacOS
  • Known bugs present in the current stable version
  • MATLAB Versions
  • NewFeatures
  • RoadMap
  • mode compute 6