-
Notifications
You must be signed in to change notification settings - Fork 705
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
MultiQC report is missing fastQC results on the dev branch #1303
Comments
Some more detail: I compared the results from the dev branch with a previous successful run using the latest release version (different data sets). The working directories are structured quite differently. Release working directory:
Dev working directory:
Despite the fact that the fastqc zip files are present in the dev working directory:
The MultiQC log doesn't show that they were found:
I also noticed that the multiQC version differs between the release (1.19) and dev (1.21) branch. I ran multQC version 1.21 manually in the working directory, and encountered the same issue where the fastQC files were not located. So, I'm not currently certain whether the issue is related to the updated MultiQC version or changes to how the working directory files are structured. Let me know if you need any additional information! |
Another update: I tried downgrading my local version of MultiQC to 1.19 (which is used in the release version of the pipeline, where it seems to be working fine) and ran it again on my working directory. The issue persists - MultiQC did not locate the fastQC files and did not incorporate them into the report. |
Thanks for reporting and the thorough investigation! I could reproduce the issue and also figured out the reason for the failed inclusion. MultiQC is run with the custom config file
In reality, the I will fix that later this week. |
Thanks a lot, Matthias! |
Just to keep you updated: I think, I fixed the bug in this branch, but the testing is somehow cursed at the moment. At first, I had issues with Nextflow not finding the images on our offline cluster and now the MultiQC reports won't load in my browser at all. (But also those from the regular pipeline). Since it seems to work for you, you are welcome to test the version from my branch. Please include also |
Hi Matthias, I cloned your fork, switched to the
Unfortunately, the fastQC results are still not present in the MultiQC report (see attached). Did I run the test correctly? Thanks! |
Thanks for testing! No, you did not do anything wrong - I did not successfully fix it. The output publishing is not working as supposed and the custom config thus does not apply. I am just working on it again, but I won't have much more time till next Wednesday for that. |
Okay, thanks for the update! Let me know if I can help with any additional testing. |
I now opened a draft PR #1308 that currently doesn't fix anything because ... that escalated quickly. There is at least one MultiQC bug (see also issue there), potentially even two, involved, and we also have additional issues with the pipeline. So unfortunately, instead of fixing one, I discovered it is a total of four issues. I described them in detail in the draft PR, so if you feel like experimenting, please give any of it a go, since I won't have time for it until end of next week. |
These bugs in MultiQC should be fixed now as of MultiQC v1.22.2 - hopefully the best solution here is to update the MultiQC nf-core module. |
#1308 has just been merged to |
Description of the bug
When running the rnaseq pipeline using the dev branch, the fastQC results are no longer included in the MultiQC report, even though the fastqc zip files are available in the results. This occurs regardless of whether trim_galor or fastp are used as the trimmer.
Command used and terminal output
Relevant files
seawulf_config.zip
nextflow.log.zip
multiqc_report.html.zip
System information
Nextflow version: 24.02.0-edge
Hardware: HPC
Executor: Slurm
Container: Singularity
OS: Rocky Linux 8.7
nf-core version: dev
The text was updated successfully, but these errors were encountered: