-
Notifications
You must be signed in to change notification settings - Fork 608
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
Hicpro MultiQC module broke #1366
Comments
Hi @RxLoutre, Sorry to hear that you're having problems. Would it be possible to attach the file that triggered the error so that I can try to replicate it? You can see the (probable) path in the error log:
Thanks, Phil |
Closing due to lack of example file to replicate the error. |
Hi Phil, I encountered the same error as @RxLoutre earlier this year when I tried to run the nf-core/hic:1.3.0 pipeline:
I didn't encounter this when I ran the pipeline with the test profile, so I wonder whether it has something to do with my data. I've attached the file that triggered this (I had to append the Thanks a lot for your help! |
Just wanted to let you know that I now know what caused this issue. With the help from @nservant, we discovered that a "_1" or "_2" in the filename will be treated as a suffix for read 1/2 files. This causes incorrect filenames along the way, which means that multiqc can't find all files it's looking for. Best wishes, |
Thanks @jzohren! Great that you got it to work. However, MultiQC shouldn't really have an unhandled crash like this, whatever you did. As you've provided a file to replicate the problem I've reopened the issue. |
Description of bug:
I have had this issue while running the nf-core for hi-c data. It ran successfully with the full dataset. I was trying to see if a subsample of the initial dataset would speed up analysis while still giving the same results, but MultiQC won't perfom on this one with the following error :
MultiQC Error log:
File that triggers the error:
MultiQC run details (please complete the following):
Additional context
It seems it actually created something as I go into the directory where the error occured, we can see a multi_qc report in there but he is an empty page with just the versions.
The text was updated successfully, but these errors were encountered: