-
Notifications
You must be signed in to change notification settings - Fork 583
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeWarning: invalid value encountered in subtract #2328
Comments
Thanks @jamigo for reporting the issue! Unfortunately, I can't figure out what might be the problem here without a reproducible example. Would you be able to share the DRAGEN QC outputs by any chance? |
By adding files one by one to MultiQC processing folder, I've traced down the error (or, at least, one of them) to a DRAGEN's sample.wgs_coverage_metrics.csv file. In fact, I think I've found the error: if I change "inf" in the "Mean/Median" ratio section to 0.5 or any other number, everything works fine. Is there any problem handling "inf" values?
If there are any others, I would be able to go on tracing issues once you suggest how to solve this one. |
@jamigo, I see now, it's indeed the Thanks again for reporting this, and thanks for narrowing down the problem! Really appreciated. Also added this example into the test bundle. |
Description of bug
Last MultiQC v1.20 update came with the need to update plotly to v5.18. It ran fine on a couple of BWA+GATK runs, but it fails on a DRAGEN run. Unfortunately, the process doesn't really break, therefore no proper MultiQC debugging information is genereated, and we don't know which module breaks and which file is triggering the error. We do see this warnings through MultiQC output that we hope you'd be able to help us understand:
The html file is generated, but it hangs at "Loading report" and no mosdepth graphs are generated. In the past, we reported another mosdepth issue with MultiQC v1.16, but v1.18 did already solve it. Could the numpy v1.26.4 be the problem? Any other ideas?
File that triggers the error
No response
MultiQC Error log
Before submitting
The text was updated successfully, but these errors were encountered: