Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need dynamic strategy for multiple variants #92

Open
tedgoldstein opened this issue Aug 30, 2016 · 3 comments
Open

Need dynamic strategy for multiple variants #92

tedgoldstein opened this issue Aug 30, 2016 · 3 comments

Comments

@tedgoldstein
Copy link
Contributor

Here is another bioinformatics issue for data sets. Handle multiple co-resident variants. For exmaple there are (at least) six variants of the APOBEC1 gene (which often uses the symbol A1CF). Most people have all of these variants.

NCBI label Hugo label
NM_138933 A1CF
NM_014576 A1CF
NM_138932 A1CF
NM_001198820 A1CF
NM_001198818 A1CF
NM_001198819 A1CF

Sometimes multiple variants need to be treated as separate genes, sometimes they should be averaged and treated as once gene. There are probably other strategies.

Rob and Holly should comment.

@rbaertsch
Copy link
Member

We should store the number of variants per gene and also store the individual variants. For protein coding variants, they are commonly stored as offset. Each isoform could have a different offset. For non-coding variants, store the offset. Important to store the truncating variants also.

@hbeale
Copy link

hbeale commented Aug 31, 2016

I'm not sure I understand the scope of the question, but everything Robert says sounds good to me. The variant nomenclature scheme at http://varnomen.hgvs.org/ is clunky but pretty good.

@mokolodi1
Copy link
Member

@tedgoldstein are the things in the first column of that table transcript labels? It doesn't seem to me that this has a compelling use case in our current roadmap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants