Skip to content
GitLab
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 118
    • Issues 118
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynareDynare
  • dynaredynare
  • Issues
  • #1682
Closed
Open
Issue created Dec 13, 2019 by Johannes Pfeifer@JohannesPfeiferDeveloper

Sort out correct order of blocks in perfect foresight Ramsey and document it

Usually steady after initval computes a steady state. But with ramsey_model, one seems to need the ramsey_model(planner_discount=0.99); statement before the call to steady and therefore initval. Also, it is not clear what steady does in this case. Is it the private sector equilibrium steady state or the Ramsey steady state that is computed. Relevant test case: optimal_policy/nk_ramsey_det.mod

Edited Dec 13, 2019 by Johannes Pfeifer
Assignee
Assign to
Time tracking