[ensembl-dev] VEP differences in REST interface (grch37 vs grch38)

[Harshit]

Please someone unsubscribe me from this list. I do not want to receive these mails at all.

Sent from Mail for Windows 10

From: Wolf Beat
Sent: 04 June 2019 20:17
To: dev at ensembl.org
Subject: [ensembl-dev] VEP differences in REST interface (grch37 vs grch38)

Hi,


i'm having an issue where several variants are missing MAF information in the grch37 rest api since the last release (they had the information previously).


One example would be:


http://grch37.ensembl.org/Homo_sapiens/Variation/Population?db=core;r=2:179616271-179617271;v=rs58651353;vdb=variation;vf=75079740


This variants shows a MAF in multiple databases on the website, yet, in the REST API it does not:

http://grch37.rest.ensembl.org/vep/hsapiens/id/rs58651353?distance=0&content-type=application/json


Yet, when accessing the latest rest backend, the information is present:


http://rest.ensembl.org/vep/hsapiens/id/rs58651353?distance=0&content-type=application/json


Are there additional parameters i have to set for the grch37 backend or is this a bug? I can give examples of more variants with that issue (eg. rs659243)


Kind regards


Beat Wolf

_______________________________________________
Dev mailing list    Dev at ensembl.org
Posting guidelines and subscribe/unsubscribe info: https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org
Ensembl Blog: http://www.ensembl.info/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20190604/b21cd93d/attachment.html>