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 5
    • Merge Requests 5
  • 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
  • Issues
  • #1756

Closed
Open
Opened Dec 15, 2020 by Johannes Pfeifer @JohannesPfeiferDeveloper

Decide what to do with options_.particles.pruning

I am having trouble with the options_.particles.pruning-option. It is used within the particle filter routines, but currently not inherited for the use of simult_ in e.g. non_linear_dsge_likelihood or irf.m. I actually don't see why we need that as a separate option of particles. I would prefer to have options_.pruning and have particles rely on it. Or to stay within the module-logic, have options_.pruning inherit options_.particles.pruning.

Assignee
Assign to
4.7
Milestone
4.7
Assign milestone
Time tracking
None
Due date
None
Reference: Dynare/dynare#1756