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 122
    • Issues 122
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • 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
  • #1758

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

Discuss moving all mod-file output to folder `M_.dname`

The discussion in !1793 (merged) points to a design problem of the generally useful M_.dname-option: We still save various output-files like the _results.mat-file in the main folder. So the dname-saving logic does not fully work. For 4.7 I would propose moving all Dynare-generated output to a subfolder of M_.dname to get a clean root directory. We have increasingly moved to the direction in the past, e.g. with the $\LaTeX$-files.

I would then also propose to offer a preprocessor command line option dname to set this at the preprocessor-level. This would allow solving the json-issue discussed at !1793 (merged)

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