Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • 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
  • #295
Closed
Open
Issue created Feb 21, 2013 by Sébastien Villemot@sebastienOwner

offer a quiet and a verbose mode

Some users who run Dynare in a loop would like to suppress all messages. On the contrary, some want more messages, for example when debugging.

We currently have a way to disable warnings (see #301 (closed)). Error messages should probably never be disabled.

For normal messages, we currently have the noprint option, but it is limited to some commands only.

I think we should provide three (global) levels of verbosity:

  • a quiet mode, with nothing printed (except warnings and error messages)
  • a normal mode
  • a verbose mode (with some debug messages or more details)

The quiet and verbose modes should probably map to equivalent options of the dynare command.

The quiet option could set options_.noprint=1 internally. The verbose option could set options_.verbose=1. Of course one can't have both quiet and verbose set at the same time.

We may want to deprecate the noprint options given at the command level. The problem is that if verbose is set at the global level, then a noprint at a local level would create many problems (in particular because all options have a global effect).

Then we have to modify the preprocessor, all M-files and MEX files to obey these two settings.

Assignee
Assign to
Time tracking