[FIX] Found errors in qc after debbuging #69
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, 👋 as requested on our latest meeting and mentioned in #58 (comment). I'm giving some attention to the qc_reports workflow.
I tried to run the pipeline normally without specifying --skip-qc so I could check if the qc report is working as normal.
I got this error message:
This error was throw because of differences into the
fastqc
outputs andmultiqc
inputs, so I emitted a new named channel so they'll match.After that The version of multiqc was giving a odd error:
which could be fixed by updating the multiqc to the latest version (v.1.12), we should check this update as it'll downgrade the picard version to 2.17, this shoudn't be a problem as the bioconda recipe for mtbseq requires picard >=2.17.0.
runing
MTBseq --check
:After those changes, I started to run mtbseq_nf again to double check if the changes into the conda env would make any change.
Happy to contribute with this work, feel free to add changes or request any modification on my approach to the errors.
Kindly, Davi