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.

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

big binary file engines #107

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from
Open

Conversation

nvictus
Copy link
Member

@nvictus nvictus commented Sep 29, 2019

Description

What was changed in this pull request?

bigWig signal and bigBed coverage tiles can be served by either pybbi or pyBigWig. Default engine is to choose whichever one is installed ("auto").

Why is it necessary?

Having alternative backends in case one library is too difficult to install on a given system.

Checklist

  • Unit tests added or updated
  • Updated CHANGELOG.md

@pkerpedjiev
Copy link
Member

Which library do you envision being installed by default?

I presume the default use case for this will be Jupyter. @mccalluc did some work moving some of the docs from the higlass repo to here so perhaps updating the section on bigWig under docs/genomic would be helpful?

@nvictus nvictus mentioned this pull request Sep 29, 2019
1 task
@nvictus
Copy link
Member Author

nvictus commented Sep 30, 2019

Which library do you envision being installed by default?

For now, let's keep bbi the default.

updating the section on bigWig under docs/genomic would be helpful

The docs for bigwigs describe ingesting via docker. I think choosing engines would be more relevant to the higlass-python/Jupyter docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants