Improve coordinate concordance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
The coordinate concordance used to be calculated relative to reference coordinates in 7.15, and will be updated to conseq coordinates in 7.16. However, both of these approaches have one drawback: we cannot calculate a concordance for insertions or deletions, respectively, because they have nothing to be compared to.
An alternative would be to extend both sequences to be the same length - that is, to fill up all deletions in both sequences with x characters - and to calculate the concordance for these two sequences. This would mean that the concordance decreases for insertions and deletions in the conseq equally - for a deletion, we would be able to tell because the window over which we average the concordance would extend into the deletion at its edge.
The advantage is that insertions and deletions would be treated "symmetrically". The difficulty will be to keep track of the true conseq coordinates and to assign the computed concordances to the correct positions. We will also have to figure out what to do with unmatched pieces of sequence. Currently, we do not compare them to anything and leave their concordance at 0.
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
Start by locating the coordinate-concordance implementation and comparing how reference coordinates in 7.15 and conseq coordinates in 7.16 are handled. Review existing coverage for insertions, deletions, and unmatched sequence pieces before defining the expected symmetric behavior. Done means concordances use aligned-length sequences while still mapping results to true conseq coordinates.
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