The output files of staramrnf are not that descriptive, such that output files are not easily distinguishable. An example issue, would be if a sample is run in multiple pipelines (e.g., IRIDA-Next), and would be difficult to determine from which pipeline outputs result from.
Solution:
Add an extension to output files .staramr. so that they can be quickly identified. E.g., sample123_detailed_summary.tsv -> sample123_detailed_summary.staramr.tsv
Additional Points:
Output files are used in nf-tests and the iridanext.output.json. The following files will need to be modified as well:
Problem:
The output files of
staramrnfare not that descriptive, such that output files are not easily distinguishable. An example issue, would be if a sample is run in multiple pipelines (e.g., IRIDA-Next), and would be difficult to determine from which pipeline outputs result from.Solution:
Add an extension to output files
.staramr.so that they can be quickly identified. E.g.,sample123_detailed_summary.tsv->sample123_detailed_summary.staramr.tsvAdditional Points:
Output files are used in
nf-testsand theiridanext.output.json. The following files will need to be modified as well:modules/local/staramr/main.nftests/main.nf.testworkflows/staramr.nfconf/iridanext.config