We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
BEDPE data is a simple format that shows interactions between two regions of the genome, and sometimes breakend data can come in this format
Small data files could be parsed in their entirety
Larger files might need a 2D index scheme (e.g. pairix).
Many applications end up with this type of data and/or a subtype of it
https://github.com/cancerit/BRASS/wiki/BEDPE https://support.10xgenomics.com/genome-exome/software/pipelines/latest/output/bedpe https://docs.higlass.io/data_preparation.html
The text was updated successfully, but these errors were encountered:
random note: possible gene fusion data from TCGA here, controlled access though cc @carolinebridge-oicr https://portal.gdc.cancer.gov/repository?filters=%7B%22op%22%3A%22and%22%2C%22content%22%3A%5B%7B%22op%22%3A%22in%22%2C%22content%22%3A%7B%22field%22%3A%22files.data_type%22%2C%22value%22%3A%5B%22Transcript%20Fusion%22%5D%7D%7D%5D%7D
Sorry, something went wrong.
just commenting here cause gene fusion discussion with @rbuels earlier too and cause the data format for these is bedpe
Successfully merging a pull request may close this issue.
BEDPE data is a simple format that shows interactions between two regions of the genome, and sometimes breakend data can come in this format
Small data files could be parsed in their entirety
Larger files might need a 2D index scheme (e.g. pairix).
Many applications end up with this type of data and/or a subtype of it
https://github.com/cancerit/BRASS/wiki/BEDPE
https://support.10xgenomics.com/genome-exome/software/pipelines/latest/output/bedpe
https://docs.higlass.io/data_preparation.html
The text was updated successfully, but these errors were encountered: