This release is a pre-release and may not be stable for production use.
tbvcfreport
A tool to generate an interactive HTML-based report from SnpEff annotated VCF file(s) with links to the Combat-TB-Explorer.
Usage
Prerequisites:
python-pip- SnpEff annotated M.tuberculosis VCF file(s).
- A Combat-TB-NeoDB instance,
tbvcfreportdefaults to neodb.sanbi.ac.za.- See combat-tb-neodb if you want a local installation and
export DATABASE_URI=localhostfortbvcfreportto use your local instance.
- See combat-tb-neodb if you want a local installation and
Installation
Using pip
$ pip install -i https://test.pypi.org/simple/ tbvcfreport
...
From source
$ git clone https://github.com/COMBAT-TB/tbvcfreport.git
...
$ cd tbvcfreport
$ virtualenv envname
$ source envname/bin/activate
$ pip install -r requirements.txt
$ pip install -e .
Run tbvcfreport
$ tbvcfreport --help
Usage: tbvcfreport [OPTIONS] COMMAND [ARGS]...
Generate an HTML-based VCF report from SnpEff annotated VCF file(s).
Options:
--help Show this message and exit.
Commands:
generate Generate an interactive HTML-based VCF report.
$ tbvcfreport generate --help
Usage: tbvcfreport generate [OPTIONS] VCF_DIR
Generate an interactive HTML-based VCF report.
Options:
-t, --tbprofiler-report FILENAME
TBProfiler json report.
-f, --filter-udi / -nf, --no-filter-udi
Filter upstream, downstream and intergenic
variants. [default: True]
--help Show this message and exit.
$ tbvcfreport generate VCF_DIR/
Processing...
This will generate a {vcf-file-name}.html file in the current working directory (pwd).
In Galaxy
🚧
We have also added tbvcfreport to the Galaxy Test Tool Shed.
Kindly see this repository for the latest revision.
Metadata
Release files for tbvcfreport 0.1.7.dev20190823
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 |
|---|---|---|---|---|
| tbvcfreport-0.1.7.dev20190823.tar.gz | 12.1 kB | Without provenance | Details for tbvcfreport-0.1.7.dev20190823.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tbvcfreport-0.1.7.dev20190823-py3-none-any.whl | Python 3 | none | any | Details for tbvcfreport-0.1.7.dev20190823-py3-none-any.whl |
Total release size: 37.4 kB
Release files / tbvcfreport-0.1.7.dev20190823.tar.gz
| Download URL | tbvcfreport-0.1.7.dev20190823.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7114e2fcd41b247439633d2b98a6ee173c6723964e555de178e00abb7090133f
|
|
BLAKE2b-256 checksum How to use checksums |
3d7ea9a20cdfcaedbac2602d99b5da0810c0e4fba11f207d6e0d1868ecbcd0e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.3
|
Release files / tbvcfreport-0.1.7.dev20190823-py3-none-any.whl
| Download URL | tbvcfreport-0.1.7.dev20190823-py3-none-any.whl |
|---|---|
| Size | 25.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab359e10a7a300c7a940f94b03dd1412a377ace1ca2066bbfc319551d6f4a60f
|
|
BLAKE2b-256 checksum How to use checksums |
401fd43c4b94584ecc7a4a510eb65f91d13c9f8ac257a565cf98be769a6aa47b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.3
|
Security for tbvcfreport 0.1.7.dev20190823
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.