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
I noticed that augur alignprints insertions to stdout, which can potentially lead to workflow logs being flooded with long insertion sequences as noted in nextstrain/hmpv#8. I think we can trim down these print statements since the same insertions are output to a file. It's not entirely clear to me from reading #449 why insertions need to be print to stdout in addition to the output CSV file.
Possible solution
Remove the print statements entirely
Only print to stdout for debugging i.e. when the command is run with the --debug flag
Keep the print statements because of (?) and always redirect stdout from augur align to a log file in workflows.
The text was updated successfully, but these errors were encountered:
Context
I noticed that
augur align
prints insertions to stdout, which can potentially lead to workflow logs being flooded with long insertion sequences as noted in nextstrain/hmpv#8. I think we can trim down these print statements since the same insertions are output to a file. It's not entirely clear to me from reading #449 why insertions need to be print to stdout in addition to the output CSV file.Possible solution
--debug
flagaugur align
to a log file in workflows.The text was updated successfully, but these errors were encountered: