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
The genome-nexus-vep supports retrieving VEP annotations by a list of variants in ENSEMBL region format only.
There is no endpoint to do it by a list of variants in hgvs format at the moment. Although the vep command that is actually used under the hood does support several formats including hgvs. See --format option here. And here is more information on how the hgvs file format should exactly look like.
The way how we pass the list of variants and in what format is the biggest differences between /vep/human/region of genome-nexus-vep and grch37.rest.ensembl.org/vep/human/hgvs/VARIANT of Ensembl API calls. See more details on differences in the comments to this ticket.
This slight difference requires genome-nexus to have 2 separate properties for each endpoint. One for the external Ensembl API call and another for the genome-nexus-vep endpoint.
It would be great to add an Ensembl API-compatible /vep/human/hgvs endpoint to genome-nexus-vep.
By having the compatible calls we can decide whether to use the external API or local version by specifying vep.url property to point to the respective url.
Despite the commentgn_vep.region.url is not respected in the all places in the application. Some features use external calls to vep.url despite gn_vep.region.url is set to get the data.
Actually, after the proposed change there might be no need in gn_vep.region.url property anymore. Many of the code that is specific to the regional endpoint in genome-nexus and genome-nexus-vep can be just removed (RegionVariantAnnotationService, CachedVariantRegionAnnotationFetcher, VEPRegionDataFetcher, ...).
The text was updated successfully, but these errors were encountered:
ruslan-forostianov
changed the title
Add endpoint to genome-nexus-vep compatible with the Ensembl /vep/human/hgvs/VARIANT call
Add an endpoint to genome-nexus-vep compatible with the Ensembl /vep/human/hgvs/VARIANT call
Jul 14, 2022
The genome-nexus-vep supports retrieving VEP annotations by a list of variants in ENSEMBL region format only.
There is no endpoint to do it by a list of variants in hgvs format at the moment. Although the
vep
command that is actually used under the hood does support several formats including hgvs. See--format
option here. And here is more information on how the hgvs file format should exactly look like.The way how we pass the list of variants and in what format is the biggest differences between
/vep/human/region
of genome-nexus-vep andgrch37.rest.ensembl.org/vep/human/hgvs/VARIANT
of Ensembl API calls. See more details on differences in the comments to this ticket.This slight difference requires genome-nexus to have 2 separate properties for each endpoint.
One for the external Ensembl API call and another for the genome-nexus-vep endpoint.
It would be great to add an Ensembl API-compatible
/vep/human/hgvs
endpoint to genome-nexus-vep.By having the compatible calls we can decide whether to use the external API or local version by specifying
vep.url
property to point to the respective url.Despite the comment
gn_vep.region.url
is not respected in the all places in the application. Some features use external calls tovep.url
despitegn_vep.region.url
is set to get the data.Actually, after the proposed change there might be no need in
gn_vep.region.url
property anymore. Many of the code that is specific to the regional endpoint in genome-nexus and genome-nexus-vep can be just removed (RegionVariantAnnotationService, CachedVariantRegionAnnotationFetcher, VEPRegionDataFetcher, ...).The text was updated successfully, but these errors were encountered: