Check if paired end reads are managed properly and if not: either fix or document properly
Open
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 4
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
- check if all steps manage the PE reads properly
- spp should not get in input paired end reads if not managed properly
- document any remaining unsolved issue
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
Start by tracing every pipeline step that consumes paired-end reads and verify whether any improperly passes them to spp. The work is done when paired-end handling is corrected where needed, or each remaining limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100