Coverage stats in output
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- bioinformatics
Research direction
No files, tests, or entry points are identified in the issue. Start by locating plassembler's output-generation path and determine what per-contig coverage statistics should be represented; done means the output includes coverage statistics for assembled plasmids.
Written by the indexing model from the issue text.
Description
Hi @gbouras13 ,
I use hybracter to assemble bacterial genomes and plasmids from long read sequencing. I want to assemble single plasmids from long read sequencing but hybracter does not work with only my small plasmids. So I used plassembler to do it.
When I use hybracter, I have an output file with coverage statistics per contig that I don't have when I use plassembler alone.
Do you think you will add this in future updates of plassembler ?
I think this is important information :)
Best regards
Corentin
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
foxglove/mcap#1907 · 1 comment ·
Maintainers usually reply within 1 day
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#14623 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
developmentseed/titiler-cmr#261 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
andrewyng/openworker#774 ·
Maintainers usually reply within 1 day
-
aggfuncOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
worldbank/blackmarblepy#160 ·