Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make sure getGeneLocation uses standard strategy to select mapping #437

Merged
merged 2 commits into from
Oct 18, 2017
Merged

Make sure getGeneLocation uses standard strategy to select mapping #437

merged 2 commits into from
Oct 18, 2017

Commits on Oct 18, 2017

  1. Add test to compare mapping chosen by getGeneLocation and numberConve… 

    …rsion

New test case where a gene has mappings to both chromosome X and Y, and
the test verifies that the same mapping is selected in API calls to
both getGeneLocation and numberConversion.
    @mkroon1
    mkroon1 committed Oct 18, 2017
    Configuration menu
    Copy the full SHA
    d64a37a View commit details
    Browse the repository at this point in the history

  2. Make sure getGeneLocation uses standard strategy to select mapping 

    When multiple mappings available, getGeneLocation now orders by
chromosome name before returning the first mapping, as is standard
for code based on Convertor._get_mapping().
    @mkroon1
    mkroon1 committed Oct 18, 2017
    Configuration menu
    Copy the full SHA
    0aa022a View commit details
    Browse the repository at this point in the history