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
  • #38
Closed
Open
Created Feb 21, 2013 by Sébastien Villemot@sebastienOwner

Allow k-order and estimation DLL to use bytecode for the model evaluation

Currently, k-order DLL and estimation DLL only work with use_dll option.

This constraint could be easily relieved by calling the M-file of the model from within the DLL, using mexCallMATLAB().

For the bytecode, a similar trick could be done, provided that support is added for 2nd and 3rd order derivatives.

From the implementation side, the idea would be to create an super class of DynamicModelDll.

This change needs to be documented in the reference manual when implemented.

Assignee
Assign to
Time tracking