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
MultiQC will parse the stdout from Kallisto (only). The Galaxy wrapper for MultiQC seems ready to do this, but the file from Kallisto is not yet available. This request is to add an option to the Kallisto tool form to write that log as a dataset in the history for use in a workflow.
We could do something similar to how HISAT2's summaries in the stderr can be output to a log output.
Alternatively: It would be super interesting to write a completely new tool that captures and writes out the stderr and/or stdout and/or info and/or description content -- from any dataset -- into the history as separate txt files. Maybe include a "stats" output with a checksum, timestamps, server/cluster details, anything else easily captured out of the technical metadata. Multi-use, we don't even need to know or care why. This probably needs a different ticket if anyone else likes the idea.
The text was updated successfully, but these errors were encountered:
toolshed.g2.bx.psu.edu/repos/iuc/kallisto_quant/kallisto_quant/0.48.0+galaxy1
MultiQC will parse the stdout from Kallisto (only). The Galaxy wrapper for MultiQC seems ready to do this, but the file from Kallisto is not yet available. This request is to add an option to the Kallisto tool form to write that log as a dataset in the history for use in a workflow.
Xref
Where the log is in the stdout
We could do something similar to how HISAT2's summaries in the stderr can be output to a log output.
Alternatively: It would be super interesting to write a completely new tool that captures and writes out the stderr and/or stdout and/or info and/or description content -- from any dataset -- into the history as separate txt files. Maybe include a "stats" output with a checksum, timestamps, server/cluster details, anything else easily captured out of the technical metadata. Multi-use, we don't even need to know or care why. This probably needs a different ticket if anyone else likes the idea.
The text was updated successfully, but these errors were encountered: