Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dynare dynare
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 108
    • Issues 108
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynare
  • dynaredynare
  • Issues
  • #1044

Closed
Open
Created Aug 28, 2015 by Johannes Pfeifer@JohannesPfeiferDeveloper

Clear up option mh_posterior_mode_estimation

See the question at http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=7235 Does anyone know what it does? Looking at the codes in dynare_estimation_1.m this option seems to skip mode computation and directly runs the MCMC, using the prior mode as the starting point and the prior variances for computing the inverse Hessian for the MCMC. In case of the mode not existing, the prior mean is used. But already before doing so, it sets

oo_.posterior.optimization.mode = xparam1;
oo_.posterior.optimization.Variance = [];

That is, the mode saved is based on the starting values given for MCMC and no variance is saved. This looks like a a bug as the MCMC starts with values that are only set after this assignment.

Finally, this option runs the MCMC and calls CutSample.m before returning. What is the point of just estimating the MCMC starting at the prior mode and providing no output?

We should either document the option and add a preprocessor command or get rid of it.

Edited Sep 01, 2021 by Johannes Pfeifer
Assignee
Assign to
Time tracking