nf-core / nf-core/seqinspector
Use MultiQC seqfu module instead of custom content to improve report
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 28
- Forks
- 44
- Avg merge
- 11d 8h
- Merged PRs (30d)
- 2
Description
I have wrote a MultiQC module for seqfu stats that was recently merged (https://github.com/MultiQC/MultiQC/pull/3271) and is part of the MultiQC v1.31 release (https://github.com/MultiQC/MultiQC/releases/tag/v1.31). This module should provide some nicer plots and sample name handling for the reports that is not possible when supplying it as "custom content" as we do currently.
The nf-core MultiQC module have no yet been updated to 1.31, but there is a raised issue here: https://github.com/nf-core/modules/issues/9014.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies the current MultiQC custom-content configuration and nf-core/modules issue 9014 as starting points; first check whether the nf-core MultiQC module supports v1.31. Replace the custom-content path with the seqfu module, then verify that reports use its plots and sample-name handling.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100