Include consensus sequences for individual regions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
We've had several users ask how to find the portion of a consensus sequence that maps to each coordinate reference. If a project has more than one coordinate reference, then include separate lines for the consensus sequence of each coordinate region, plus the full seed. That will also make the headers of the FASTA downloads simpler.
Contributor guide
No contributing guide indexed for this repository
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 locating the consensus-sequence generation and FASTA download entry points in MiCall, then trace how projects with multiple coordinate references are represented. Done means each coordinate region has its own consensus line, alongside the full seed, with simpler FASTA headers; no specific files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100