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
Thanks for this great tool. I've noticed a bug which seems to arise from a parsing error of qualimap RNAseq output. If I understood correctly, MultiQC parses the rnaseq_qc_results.txt from qualimap rnaseq analysis. But the authors of qualimap have separated the hundreds by a space, thus the counts displayed in MultiQC's report based on qualimap RNAseq output are incorrect. I guess the regex that is being used stops at blanks.
Instead of [\d,] need [\d, ] (not sure if anything special is needed for the non-breaking space). Then need to strip the spaces afterwards for proper Python float handling.
Looks like we already have support for sorting out . thousands separators:
Description of bug
Hello,
Thanks for this great tool. I've noticed a bug which seems to arise from a parsing error of qualimap RNAseq output. If I understood correctly, MultiQC parses the
rnaseq_qc_results.txt
from qualimap rnaseq analysis. But the authors of qualimap have separated the hundreds by a space, thus the counts displayed in MultiQC's report based on qualimap RNAseq output are incorrect. I guess the regex that is being used stops at blanks.Example of qualimap RNAseq output:
Numbers reported by MultiQC:
The MultiQC version I use is
1.14
, installed with miniconda.Best,
Florian
File that triggers the error
rnaseq_qc_results.txt
MultiQC Error log
Before submitting
The text was updated successfully, but these errors were encountered: