Added nuclear_contamination to MultiQC report as custom content. #511
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.
Various changes:
environment.yaml
. This version doesn't fail horribly when a bin has 0 coverage, instead setting the rates to 0.snp_counts
) from multiqc_report. Not that useful, but easier to hide it than to change MQC modules.Nuclear_contamination changes:
To Do:
-profile test_tsv_humanbam
, library entry is correctly assigned,but individual level entry has_rmdup
added to Sample ID in the JSON. Looking into it.PR checklist
nextflow run . -profile test,docker --paired_end
).nf-core lint .
).docs
is updatedCHANGELOG.md
is updated