[ensembl-dev] Ensembl REST API | Bug in ld/:species/pairwise/:id1/:id2?
anja at ebi.ac.uk
Thu Jul 18 10:20:18 BST 2019
this is not a bug as such because we did not intend to keep the order of the input variants which we loose in our internal LD calculations. But I absolutely agree that this is causing confusions and we will update the endpoint to retain the order of the input variants in the output. This will be updated for our 98 release planned to be out in September.
> On 17 Jul 2019, at 17:41, Ramiro Magno <ramiro.magno at gmail.com> wrote:
> It seems that the response returned by this endpoint:
> http://rest.ensembl.org/documentation/info/ld_pairwise_get <http://rest.ensembl.org/documentation/info/ld_pairwise_get>
> does not always respect what is variant id1 and variant id2.
> https://rest.ensembl.org/ld/human/pairwise/rs1042779/rs62255400?population_name=1000GENOMES:phase_3:CEU;d_prime=0;r2=0 <https://rest.ensembl.org/ld/human/pairwise/rs1042779/rs62255400?population_name=1000GENOMES:phase_3:CEU;d_prime=0;r2=0>
> As per the documentation, I was expecting variant1 = rs1042779, and variant2 = rs62255400 but the actual response is:
> d_prime: '0.999977'
> population_name: 1000GENOMES:phase_3:CEU
> r2: '0.271200'
> variation1: rs62255400
> variation2: rs1042779
> The two variants are swapped.
> Can you confirm this is a bug?
> Cheers, Ramiro
> 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...
More information about the Dev