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
{{ message }}
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
Is there a way to have pypeflow's logger messages sent to a file instead of stderr other than just doing it on the command line? Even better, can just logger info messages be sent to a file, and warning/fatal ones be sent to stderr?
The text was updated successfully, but these errors were encountered:
Yes, that's all completely configurable. Look first at logging.ini in FALCON-examples. (Even if you aren't using that package, you can use the configuration there.) It sends some logging to stderr, above some level, and the more detailed logging (along with the less detailed) is split into 2 files, depending on the source.
…er to develop
* commit '790032c6023a2fd51949d63fdb05c5b2a6b483a0':
The defaults of graph_to_contig.py now generate proper p_ctg and improper a_ctg, which should be the correct behaviour. The first read of an a_ctg is completely included in the collapsed region of the corresponding p_ctg right up until the fork.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a way to have pypeflow's logger messages sent to a file instead of stderr other than just doing it on the command line? Even better, can just logger info messages be sent to a file, and warning/fatal ones be sent to stderr?
The text was updated successfully, but these errors were encountered: