Confusion frequently arises around the auto strandedness detection from Salmon and how it matches (or rather does not) with that from RSeQC towards the end of the pipeline. It would help if we could at least show the Salmon-detected strandedness in the MultiQC report.
This requires:
MultiQC to detect and report strandedness from Salmon
The pipeline to be rewired to pass the Salmon JSON files from the subsampling/ Salmon workflow (not the main Salmon process used for quantification) to MultiQC show the results and distinguish them from the Salmon results from quantification.
1) should have been done, already, but there was a bug in MultiQC (now fixed), and we'll need a new release for that to be resolved fully.
Description of feature
Confusion frequently arises around the auto strandedness detection from Salmon and how it matches (or rather does not) with that from RSeQC towards the end of the pipeline. It would help if we could at least show the Salmon-detected strandedness in the MultiQC report.
This requires:
1) should have been done, already, but there was a bug in MultiQC (now fixed), and we'll need a new release for that to be resolved fully.
I suspect 2) is going to be fiddly.