cfe-lab / cfe-lab/MiCall

Add insertion sequence to nuc.csv and amino.csv

Open
#768 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
21
Forks
11
Avg merge
12h 5m
Merged PRs (30d)
24

Description

Currently, insertions in the consensus relative to the reference are reported in nuc.csv and amino.csv as counts in the insertions column, but the actual insertion sequence is not included. Users have reported back that it would be useful to have access to the sequence of the consensus insertion in these files as well.

Add the consensus insertion sequence in nuc.csv and amino.csv, with their respective consensus coordinates and blank reference coordinates - this is equivalent to how deletions are treated, with blank consensus positions. Think about how to use the insertions column in these cases - should it report the total insertions count for the insertion positions only (in contrast to reporting insertions after a certain position right now)?

This could be implemented in the same way that insertions are handled for the stitched consensus, by adding them into the region nucleotides and aminos with non-integer positions, so they end up between the correct reference positions.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Trace the code that generates nuc.csv and amino.csv, then compare it with how insertions are represented in the stitched consensus and in the region nucleotides and aminos. The work is done when consensus insertion sequences appear at their consensus coordinates with blank reference coordinates in both files, with insertion counts behaving consistently for insertion positions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
bioinformatics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.