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 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • Dynare
  • dynaredynare
  • Issues
  • #1818
Closed
Open
Created Sep 22, 2021 by Sébastien Villemot@sebastienOwner

Decide what to do with solve_algo=13

solve_algo=13 uses the block_trust_region MEX, which is essentially a MEX reimplementation of what is available under solve_algo=4.

After a Mattermost discussion on 2021-09-21/22, the consensus seems to be:

  • verify that the two codes are really equivalent (in particular when moving in the complex domain)
  • then change solve_algo=4 so that it calls the MEX file, and drop solve_algo=13
  • the old MATLAB code for solve_algo=4 should be kept under missing/mex, ideally with an interface, in order to facilitate the debugging of models (which is easier in MATLAB than in Fortran)
Assignee
Assign to
Time tracking