ISEQcBioPortal
Scripts that allow you to:
- Create/Update database from cBioPortal
- Annotate VCF with information such as:
- number of samples with one or more mutations
- percentage of samples with one or more mutations
Install iseqcbioportal library
Optional steps (create virtual environment):
python3 -m venv venv
source venv/bin/activate
Obligatory steps:
python3 -m pip install --upgrade pip
pip3 install iseqcbioportal
Requirements
- python >=3.6
- pandas >= 1.4.2
- requests >= 2.28.1
- SQLAlchemy >= 1.4.0
- loguru >= 0.6.0
- pysam >= 0.21.0
Create databases
create_cbioportal_database
Annotate VCF
vcf_annotate_cbioportal --input-vcf "/path/to/input.vcf.gz" \
--studies "studyId" \
--output-vcf "/path/to/output.vcf.gz"
Metadata
Release files for iseqcbioportal 0.0.6
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 |
|---|---|---|---|---|
| iseqcbioportal-0.0.6.tar.gz | 6.7 kB | Without provenance | Details for iseqcbioportal-0.0.6.tar.gz |
Release files / iseqcbioportal-0.0.6.tar.gz
| Download URL | iseqcbioportal-0.0.6.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
317e783bd604c5f3f594a1adee19d81fabf99b7858902303e9cad75094417b2b
|
|
BLAKE2b-256 checksum How to use checksums |
defb8b1e966ec6da7e953c79c7b9ef8635d9bc0724ab13df7739205e0935772a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for iseqcbioportal 0.0.6
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.