Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-rest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl-rest
  • Issues
  • #276

Closed
Open
Created Jul 28, 2018 by Marek Szuba@mks

Potential issue with LD functions

Created by: hsinyen

Thank you for this wonderful API, it's been very useful! I am finding that it seems to "miss" some SNPs when I use _GET ld/:species/:id/:population_nam_e in humans.

For example, rs492400 and rs600057 are 100k bps apart and have high ld (r2=1.0, d_prime= 1.0 in CEU). However, when I try to run GET ld/:species/:id/:population_name on rs492400, rs600057 never pops up in the result, regardless of which 1000G population I use. It also doesn't work if I try to run the function on rs600057.

I'd really appreciate your help!

Assignee
Assign to
Time tracking