New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not figure out read 2 length from RunInfo.xml #2508
Comments
It appears that the bcl-convert module of MultiQC is making the assumption that there is a As shown above, the RunInfo.xml for this NextSeq2k run simply includes |
Thanks a lot for the bug report @nick-youngblut! This should fix it: #2511 (and potentially other bugs related to uncommon combination of index and non-index reads). Before I merge, can you please add your test example to https://github.com/MultiQC/test-data to make sure the fix works? |
I'm not sure where to put the file or how to name it. Should it go in https://github.com/MultiQC/test-data/tree/main/data/modules/bclconvert/3.9.3? The RunInfo.xml file is simply:
...or any other RunInfo.xml file that just includes:
...will result in the same MultiQC error:
|
The location doesn't matter, you can even attach them here to a comment. I really just wanted to test on a real life output with this set up, to see if other files would break as well (e.g. Quality_Metrics.csv, Adapter_Metrics.csv). Plus, the module wouldn't run at all without Also, not relevant for Xml, but generally it's better to attach files as is, rather than copy the contents into a comment, because GitHub messes with spacing, and for many file types the concrete form of indentation matters. |
@vladsavelyev any idea when the new release of MultiQC will be published? I am using the MultiQC biocontainer for my Nextflow pipeline, and I'd rather use the biocontainer versus creating a custom Docker container with the most recent version of MultiQC. |
Description of bug
Running MultiQC on bcl-convert output.
The error:
The top of the RunInfo.xml file:
The RunInfo.xml file clearly shows the read 2 length, so it appears that MultiQC has a bug, or at least is generating a misleading error message.
File that triggers the error
No response
MultiQC Error log
The text was updated successfully, but these errors were encountered: