question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

HGNC gene mapping in hg38

See original GitHub issue

When using hg38 cases in Scout we have noticed that some genes aren’t mapped to the gene symbol. Like this: bild

It seems it is using the hg19 data to do the ID<->symbol mapping, as it is the default of hgnc_genes(), hgnc_gene() and hgnc_id() functions. And in most places where these functions are used, no build version is given.

My naive solution to this would be to, in all places these functions are used, change for example:

hgnc_gene = store.hgnc_gene(xxx)

to

genome_build = case_obj.get('genome_build', '37')
hgnc_gene = store.hgnc_gene(xxx, build=genome_build)

But I’m not confident this is the right solution. Any input appreciated!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
bjhallcommented, Feb 24, 2020

Thanks @northwestwitch for looking at this! I started digging in it last week but was slightly overwhelmed by many places that needed to be fixed, and I didn’t really understand what some of them were doing. And some of them were not in the context of a case (mainly panel stuff), so I wasn’t sure how to treat those either.

In addition to hgnc_gene(), the following functions also take an optional “build” parameter, which as far as I can tell appear to have been left out in a few places throughout the code. I’m not sure if they are relevant, but it’s an observation I made…

hgnc_id()
all_genes()
hgncid_to_gene()
gene_by_alias()
genes_by_alias()
0reactions
northwestwitchcommented, Feb 24, 2020

Thanks, I’ll look into these functions as well! It is a bit overwhelming, I agree! The easiest would be to modify in the code the default params from “37” to “38”. The problem is that we can’t since our pipeline is still using build 37. But fixing here and there should work, eventually!

Read more comments on GitHub >

github_iconTop Results From Across the Web

HUGO Gene Nomenclature Committee: Home
The HGNC is a resource for approved human gene nomenclature containing ~42000 gene symbols and names and 1300+ gene families and sets.
Read more >
Genenames.org: the HGNC and VGNC resources in 2019
The HUGO Gene Nomenclature Committee (HGNC) based at EMBL's European Bioinformatics Institute (EMBL-EBI) assigns unique symbols and names to ...
Read more >
Gene tracks - Genome Browser FAQ
The "UCSC Genes" track, also called "Known Genes", is available only on assemblies before hg38. It was built with a gene predictor developed...
Read more >
Gene Annotation & Mapping - Cancer Dependency Map
All genes have an internal ID, allowing mapping to current and previous HGNC gene symbols, Ensembl Gene IDs (v91) and other external gene...
Read more >
05: Bioconductor Annotation Resources
Hs.eg.db , the central identifier is the Entrez gene identifier, and to map from, say HGNC Symbol to Ensembl identifier, a map must...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found