metro map to reflect conditional branch?
Open
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 16
- Forks
- 27
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
the metromap doesn't reflect the seqtk stage is conditional.
it also suggests that multiqc operates on the output of seqtk, which
is trimmed, i.e. not raw, reads. Something like this perhaps?
+--------------+ +--------------+
| | | |
| | | |
| | | |
| fastqc |--------------| multiqc |-----------
| | | |
| | | |
| | | |
+--------------+ +--------------+
|
|
|
|
|
|
+--------------+
| |
| |
| |
| seqtk |----------------------------------------------
| |
| |
| |
+--------------+
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
Locate the source for the current metro map and inspect how the workflow stages are represented. Update the diagram to show that seqtk is conditional and that multiqc uses the raw-read FastQC output rather than seqtk's trimmed reads; done means the map accurately reflects both paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100