We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Is the "both" choice relevant?
tail -f <logfile>
tee
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.
Sorry, something went wrong.
I propose to clarify the verbosity policy of MATAM as follows:
Add a fileHandler to the logger #26
d612138
Update logging messages accordingly to the new verbosity policy #26
d3bc7d1
loic-couderc
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: