Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-io
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • 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
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • 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-io
  • Merge requests
  • !62

Changes required to support bigInteract format - ENSWEB-4751

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Marek Szuba requested to merge github/fork/ens-ap5/feature/bigInteract into master Aug 02, 2018
  • Overview 8
  • Commits 5
  • Pipelines 0
  • Changes 6

Created by: ens-ap5

Description

Extend the BED/bigBed parsers to allow location data to be retrieved by column index.

Use case

UCSC have introduced another variation on bigBed format, designed for use with long-range interactions. However as part of their specification they encourage their users to set their own column names in the AutoSQL for the source and target locations, meaning that our web code cannot rely on using the default column names to fetch this data. See https://genome.ucsc.edu/goldenpath/help/interact.html

We must therefore rely on the column index alone, which is not currently supported by the bed-like parsers.

Benefits

Enables us to support this new format in the browser.

Possible Drawbacks

Perhaps not the most elegant solution, but the changes to the BED parser are mainly to keep things DRY. We need to convert UCSC chromosome names into Ensembl ones, and zero-based coordinates into Ensembl coordinates, so being able to do this for any arbitrary column saves repeating code in the bigBed parser.

Testing

I've run the bed.t and bigbed.t tests, which passed successfully. I'm not aware of any other tests that would be affected by this change since it's specific to these formats.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/ens-ap5/feature/bigInteract