You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been running VEP v113 using the cache and docker image, and I've found some variants that are present in gnomAD v4.1 but are absent from the cache.
Example 1: 20:45891598:CCTG:C the co-located variant is flagged in Ensembl, I have now added in --failed 1 to my VEP command and I expect this variant will now have AFs.
Example 2: 8:144392334:T:TGGGGGTGCAAGGTGA this variant is present in gnomAD but is not in dbSNP
Example 3: 1:9244919:CCCCAGGCA:C this variant is present in gnomAD and ClinVar, but is not in dbSNP
On this page: https://useast.ensembl.org/info/docs/tools/vep/script/vep_cache.html#cache in the "Data in the cache" section, it lists the sources of variants in the VEP cache, and this includes dbSNP, ClinVar, and gnomAD v4.1. I would therefore assume that any variant in any of these sources should be present in the cache, however what I've observed is that the variant has to be present in dbSNP to be in the cache - which is the expected behaviour?
I would really like to avoid having to add the gnomAD AFs as a custom annotation as I imagine this is going to add quite a bit of processing time to the annotation, but we're missing AFs from quite a few variants which is having a knock-on effect for our variant filtering processes.
Thanks!
Suzy
The text was updated successfully, but these errors were encountered:
Hi @suzyhh,
That is correct, variants must be present in dbSNP to be included in the cache. For VEP cache version 113 the corresponding dbSNP version is 156.
Unfortunately, the only way to obtain the gnomAD annotation is by using the custom annotation.
Testing the example variants with custom annotation, I can find the following matches:
Hello,
I've been running VEP v113 using the cache and docker image, and I've found some variants that are present in gnomAD v4.1 but are absent from the cache.
Example 1:
20:45891598:CCTG:C
the co-located variant is flagged in Ensembl, I have now added in--failed 1
to my VEP command and I expect this variant will now have AFs.Example 2:
8:144392334:T:TGGGGGTGCAAGGTGA
this variant is present in gnomAD but is not in dbSNPExample 3:
1:9244919:CCCCAGGCA:C
this variant is present in gnomAD and ClinVar, but is not in dbSNPOn this page: https://useast.ensembl.org/info/docs/tools/vep/script/vep_cache.html#cache in the "Data in the cache" section, it lists the sources of variants in the VEP cache, and this includes dbSNP, ClinVar, and gnomAD v4.1. I would therefore assume that any variant in any of these sources should be present in the cache, however what I've observed is that the variant has to be present in dbSNP to be in the cache - which is the expected behaviour?
System
Full VEP command line
I would really like to avoid having to add the gnomAD AFs as a custom annotation as I imagine this is going to add quite a bit of processing time to the annotation, but we're missing AFs from quite a few variants which is having a knock-on effect for our variant filtering processes.
Thanks!
Suzy
The text was updated successfully, but these errors were encountered: