You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If MIRCO is used as a standalone solver, it might be fine to just write output to the screen. However, when being used as micro-scale solver within 4C, it is probably desirable to turn off MIRCO output (or at least to be able to control the amount of output).
Therefore, I propose to introduce different levels of verbosity (e.g. none, medium, extreme), so that the user can decide at runtime, how much information shall be printed to the screen.
There are several options to implement that on a technical level. Let's first clarify, whether we need or want control over verbosity, and look into technical options later.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
If MIRCO is used as a standalone solver, it might be fine to just write output to the screen. However, when being used as micro-scale solver within 4C, it is probably desirable to turn off MIRCO output (or at least to be able to control the amount of output).
Therefore, I propose to introduce different levels of verbosity (e.g. none, medium, extreme), so that the user can decide at runtime, how much information shall be printed to the screen.
There are several options to implement that on a technical level. Let's first clarify, whether we need or want control over verbosity, and look into technical options later.
Beta Was this translation helpful? Give feedback.
All reactions