Add support for switching RLE subunit between largest and smallest
@theferrit32 is already working on this.
Since Jul 2, 2026.
Assessment
This issue has not been assessed yet.
Description
The code right now uses the largest subunit obtained after trimming common sequence.
The goal of this issue is to add support for instead using the smallest. This will then be made the default when we update to a forthcoming spec version, and will enable us to support creating digests using the prior 'largest subunit' method optionally in the code, when that is requested.
See https://github.com/ga4gh/vrs-python/issues/549#issuecomment-2810682997 for prior discussion.
- Dominant language
- Python
- Stars
- 63
- Forks
- 43
- Avg merge
- 1h 2m
- Merged PRs (30d)
- 1
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.
More from ga4gh/vrs-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ga4gh/vrs-python#653 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ga4gh/vrs-python#540 · 8 comments ·
-
enhancement
ga4gh/vrs-python#651 · 1 comment · 1 assignee ·
-
ga4gh/vrs-python#641 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ga4gh/vrs-python#640 ·
All issues in ga4gh/vrs-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100