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 117
    • Issues 117
    • 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
  • #1276
Closed
Open
Issue created Sep 02, 2016 by Marco Ratto@rattomaDeveloper

bug in conditional forecast

The conditional forecast is buggy.

Namely there is some inconsistency in indexing between decision rule and declaration order.

The way to fix it is to make sure that the pre-processor sets the vector of indices: constrained_vars_ in decision rule order. In fact, imcforecast assumes that constrained_vars_ is in decision rule order Moreover, one needs to fix imcforecast for the trend, since the latter is already defined in decision-rule ordering (so no need to use inv_order_var). I am going to make a pull request with the imcforecast fix, but I do not touch the pre-processor. If someone (@houtan?) could help with the latter. Many thanks

Assignee
Assign to
Time tracking