direct ROH
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Consider storing ROH directly instead of series of sums.
| Start | End | StartM | EndM | length | lengthM | iid | ch | StartPosGRCh37 | EndPosGRCh37 |
|---|---|---|---|---|---|---|---|---|---|
| 5132 | 13807 | 0.312264 | 0.57488501 | 8675 | 0.26262101 | example | 18 | 10330738 | 38202500 |
| 8294 | 15744 | 0.385997 | 0.57195503 | 7450 | 0.18595803 | example | 20 | 16217910 | 39041871 |
Need StartM, EndM, ch, maybe start and end positions.
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
No file or test is named. Start by locating how ROH is currently represented as a series of sums, then compare that representation with the example rows and required fields: StartM, EndM, chromosome, and possibly start and end positions. Done means the storage design and affected data are clearly defined and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100