BBQ (BetterBaseQuals)
A somatic SNV variant caller that uses discordant overlapping read pairs to calculate sample-specific base error rates.
Requirements
bbq requires Python 3.8 or above.
Install
bbq can be installed using pip:
pip install betterbasequals
or using pipx:
pipx install betterbasequals
Usage
The bbq tool has different commands that can be run. To get at list of the different command you can use -h or --help:
bbq -h
To see the options for a specific command you can use -h after a command:
bbq count -h
To call variants in a sample you will need to first gather training data then train the model on the sample and finally call variants using the model. Typically you will want to split this into multiple jobs and we recommend using the snakemake workflow bbq_pipeline that does this. That github project also contain training data that can be used to test BBQ.
If you want to run both the error counting, model training and variant calling using a single command that is also possible using the following command (but we strongly recommend using the above mentioned workflow):
bbq call --bam_file cfdna.bam --filter_bam_file pbmc.bam --twobit_file ~/Data/2bit/hg38.2bit
For some of the command it is possible to run it on only a part of the genome using the -r {chrom}:{start}-{end} option Fx:
bbq call_only --bam_file tmp.bam --twobit_file ~/Data/2bit/hg38.2bit --input_file_kmerpapa model.txt -r chr22:30000000-31000000
Several of the commands requires the reference genome in 2bit format. If the bam file is mapped to a known reference genome the 2bit file can be downloaded from:
https://hgdownload.cse.ucsc.edu/goldenpath/{genome}/bigZips/{genome}.2bit where {genome} is a valid UCSC genome assembly name (fx. "hg38").
Otherwise a 2bit file can be created from a fasta file using the faToTwoBit command. A linux binary of the tool can be downloaded from UCSC:
wget https://hgdownload.cse.ucsc.edu/admin/exe/linux.x86_64/faToTwoBit
Metadata
Release files for betterbasequals 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| betterbasequals-0.3.0.tar.gz | 31.6 kB | Without provenance | Details for betterbasequals-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| betterbasequals-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for betterbasequals-0.3.0-py3-none-any.whl |
Total release size: 67.1 kB
Release files / betterbasequals-0.3.0.tar.gz
| Download URL | betterbasequals-0.3.0.tar.gz |
|---|---|
| Size | 31.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
510c1f6329bb646529e3ba7e4d7c84840910010922bc13c2717762f58a2956bc
|
|
BLAKE2b-256 checksum How to use checksums |
0c50e22ffd7fe863886957c68e81e975d52bdd4eb5faa60a759f3474bd2f4fd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.9.15 Darwin/24.3.0
|
Release files / betterbasequals-0.3.0-py3-none-any.whl
| Download URL | betterbasequals-0.3.0-py3-none-any.whl |
|---|---|
| Size | 35.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b709dad043b21600faaa35c1a145aae57dc18b72cb43ea56f4fe8e765888ab86
|
|
BLAKE2b-256 checksum How to use checksums |
cd14641da880ce12f72fbcca3d7e48bf96abb5cb94c33ed3987913d7afc6c7f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.9.15 Darwin/24.3.0
|
Security for betterbasequals 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.