Multiple chromosomes - combined reference for even copy number distribution
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- bioinformatics
Research direction
Start by locating the plasmid copy-number calculation and the code that selects chromosomal contigs. Determine how multiple chromosomes are represented and how combined coverage should affect even copy-number distributions. Done means the calculation uses all relevant chromosomal contigs for multi-chromosome bacteria without changing single-chromosome behavior; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Description
For bacteria with multiple chromosomes, perhaps calculate plasmid copy number based off the combined chromosomal contigs, not just the first one.
- Dominant language
- Python
- Stars
- 91
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from gbouras13/plassembler
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
gbouras13/plassembler#71 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
gbouras13/plassembler#62 · 10 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
gbouras13/plassembler#56 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
gbouras13/plassembler#55 · 5 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
gbouras13/plassembler#54 · 1 reaction ·
All issues in gbouras13/plassembler
Similar issues
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramnes/notion-sdk-py#423 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
duckdb/duckdb-web#7514 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jbacalso24/mimry#525 ·
Maintainers usually reply within 1 day