Roadmap: Planned Features & Milestones
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, javascript, rust, wasm
- Domain
- bioinformatics, data-visualization
Research direction
This is a roadmap checklist, not a task, and it names no files or entry points. Before starting, ask the maintainer which single unchecked item they want and open a separate issue for it. Only then read the parser code that item touches and the existing tests for it. Done means that item is implemented, tested, and checked off here.
Written by the indexing model from the issue text.
Description
Core Infrastructure
using Async where possible, parsing bioinformatic file types
- Genbank parser
- Embl parser
- Conversions of formats into gbk/embl/fasta/ffn/faa and save as gff/gbk or embl
- CI/CD with github actions and write tests - ongoing
- Documentation with examples - ongoing
Format expansion
Integration of common types and parsers such as:
- VCF
- BLAST output in various modes, -5 (XML) and -6 (one line per hit), compat with Diamond, MMSeqs2
- GTF
- link ups with formats from rust-bio, noodles-vcf
- look into metabolomics options (like KEGG) some are not open-source
- fastq gzipped version parsing
- SAM format parser
- RPKM output parser
- Support for other compressed files such as BAM and CRAM
- Writer support for those types
Advanced features
Protein parameters such as:
- Hydrophobicity
- Molecular weight
- Counted amino acids & as percentage
- Aromaticity
- Parsing phylogenetic trees
- Parsing multiple sequence alignments
- Methylation data parsing
- Consider pyo3 integration
Testing - bioinformatics
- Testing & updating parsers with various edge case files such as gbk with the CONTIG(JOIN) structure
Data Viz
- Example heatmap with WASM and Js example
- Simple graph types bar, line, scatter
- Dominant language
- Rust
- Stars
- 38
- Forks
- 15
- Avg merge
- 21h 33m
- Merged PRs (30d)
- 2
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 LCrossman/microBioRust
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
LCrossman/microBioRust#57 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LCrossman/microBioRust#53 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
LCrossman/microBioRust#51 ·
-
legacy manual annotation format rare error missing last codon in pseudogene after genbank! parseOpen
Difficulty 3/5 Half a day Newbie friendliness 40/100
LCrossman/microBioRust#50 ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 25/100
LCrossman/microBioRust#19 ·
All issues in LCrossman/microBioRust
Similar issues
-
documentation priority:p2 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
dispatch:sol-high documentation
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
carrick-sh/carrick#768 · 1 comment ·
Maintainers usually reply within 1 day
-
correctness postgres tursopg
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tursodatabase/turso#10442 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
ankitects/anki#5864 · 1 reaction ·
Maintainers usually reply within 2 days
-
area: config effort: S good first issue P3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ferenyl/azuredevopstui#63 ·