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
  • #917

Closed
Open
Created May 02, 2015 by Johannes Pfeifer@JohannesPfeiferDeveloper

Add indicator for successful run of MCMC to mh_history_

Currently, at the beginning of the MCMC we use metropolis_hastings_initialization to write a new mh_historyfile. But we never confirm that this run was successful. When using the load_mh_file this leads to cryptic crashes. I would propose to add an indicator for a non-crashed run to the history file and check this indicator when load_mh_file is requested. If the indicator shows a non-successful run, we should recommend either using the mh_recover option or to delete the most recent history file to make Dynare try to access the previous, hopefully successful run.

Assignee
Assign to
Time tracking