Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate the STDOUT and STDERR outputs in a log file #26

Closed
ppericard opened this issue Jun 23, 2017 · 2 comments
Closed

Duplicate the STDOUT and STDERR outputs in a log file #26

ppericard opened this issue Jun 23, 2017 · 2 comments
Assignees
Milestone

Comments

@ppericard
Copy link
Member

ppericard commented Jun 23, 2017

We should have a log file to store everything that currently output to STDOUT and STDERR.

Currently, if people dont redirect their STDOUT and STDERR in a file, they can lose important informations about the run.

The implementation should be fexible enough so that it is easy to chose whever we want to output to the terminal or to the log file, or both.

@loic-couderc
Copy link
Member

Is the "both" choice relevant?

  • logging to a file: then use tail -f <logfile> to see the ouput in the terminal.
  • logging to terminal: then use tee to duplicate the output:
matam_assembly.py ... | tee <logfile>

Only the second case could be problematic in the way that you have to know what you want when you run the command.

@loic-couderc
Copy link
Member

loic-couderc commented Oct 26, 2017

I propose to clarify the verbosity policy of MATAM as follows:

  • default: log all messages with an INFO level or above. (currently not the case: WARNING or above)
  • verbose:
    • increase the verbosity of the tools used by MATAM (mainly first level tools)
    • log stdout/stderr of this tools
    • show final stats
  • debug:
    • verbose mode + log all messages with DEBUG level or above (typically, command lines etc...).
    • use a logger formatter with more info (time, module...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants