OncodriveFML
Recent years saw the development of methods to detect signals of positive selection in the pattern of somatic mutations in genes across cohorts of tumors, and the discovery of hundreds of driver genes. The next major challenge in tumor genomics is the identification of non-coding regions which may also drive tumorigenesis. We present OncodriveFML, a method that estimates the accumulated functional impact bias of somatic mutations in any genomic region of interest based on a local simulation of the mutational process affecting it. It may be applied to all genomic elements to detect likely drivers amongst them. OncodriveFML can discover signals of positive selection when only a small fraction of the genome, like a panel of genes, has been sequenced.
License
OncodriveFML is made available to the general public subject to certain conditions described in its LICENSE. For the avoidance of doubt, you may use the software and any data accessed through UPF software for academic, non-commercial and personal use only, and you may not copy, distribute, transmit, duplicate, reduce or alter in any way for commercial purposes, or for the purpose of redistribution, without a license from the Universitat Pompeu Fabra (UPF). Requests for information regarding a license for commercial use or redistribution of OncodriveFML may be sent via e-mail to innovacio@upf.edu.
Usage
OncodriveFML is meant to be used through the command line.
By default, OncodriveFML is prepared to analyse mutations using HG19 reference genome. For other genomes, update the configuration accordingly.
Running OncodriveFML without installation (using Docker)
You can run OncodriveFML without having to install anything in your machine if you have Docker installed.
This is how you would run the example included in this repository:
docker run --rm -i \
-v ${BGDATA_LOCAL:-${HOME}/.bgdata}:/root/.bgdata \
-v $(pwd)/example:/data \
--workdir /data \
bbglab/oncodrivefml:2.5.0 \
-i paad.txt.gz -e cds.tsv.gz --signature-correction wx --seed 123 --force
-v ${BGDATA_LOCAL:-${HOME}/.bgdata}:/root/.bgdata will allow the docker
container to see the contents of your bgdata directory as defined by the
environment variable BGDATA_LOCAL (or if it is not defined, the default
~/.bgdata).
-v $(pwd)/example:/data will allow the docker container to see the example data
in ./example. You would need to replace $(pwd)/example by the folder where
you have your own data.
--workdir /data will set the working directory to the data folders you
specified before.
The results will be saved in a folder named cds under the ./example folder.
Installation
OncodriveFML can work with the Python versions 3.8 up to 3.11 (included).
The easiest way to install all this software stack is using the well known Anaconda Python distribution
conda install -c bbglab oncodrivefml
OncodriveFML can also be installed using pip:
pip install oncodrivefml
Finally, you can get the latest code from the repository and install it in development mode:
git clone https://github.com/bbglab/oncodrivefml.git
cd oncodrivefml
make build-dev
source .venv/bin/activate
oncodrivefml --help
Running the example
Download and extract the example files (if you cloned the repository skip this step):
wget https://github.com/bbglab/oncodrivefml/archive/refs/tags/2.5.0.tar.gz
tar xvzf 2.5.0.tar.gz
To run this example OncodriveFML needs all the precomputed CADD scores, that is a 17Gb file, that will be downloaded automatically, together with the reference genome.
To run the example, we have included a bash script (run.sh)
that will execute OncodriveFML. The script should be executed in
the folder where the files have been extracted:
cd oncodrivefml-2.5.0/example
./run.sh
The results will be saved in a folder named cds.
Configuring OncodriveFML
Although OncodriveFML includes a predefined configuration file, it is highly recommended to create one yourself. In fact, if you are interested in using a reference genome other than HG19, or a score other than CADD 1.0, it is mandatory. See the documentation for the configuration for more details.
Documentation
Find OncodriveFML documentation in ReadTheDocs.
You can also compile the documentation yourself using Sphinx, if you have cloned the repository. To do so, run the following command:
make docs
open docs/build/html/index.html
Metadata
Release files for oncodrivefml 2.5.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 |
|---|---|---|---|---|
| oncodrivefml-2.5.0.tar.gz | 606.8 kB | Without provenance | Details for oncodrivefml-2.5.0.tar.gz |
Built distributions (wheels)
Total release size: 10.8 MB
Release files / oncodrivefml-2.5.0.tar.gz
| Download URL | oncodrivefml-2.5.0.tar.gz |
|---|---|
| Size | 606.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b6eed423239adeaa29bc6694dac229bcba028f4bd3ce4b62427edf37890348b
|
|
BLAKE2b-256 checksum How to use checksums |
17dffb8625dbfba5e5ef968fd1254f12a0def06ef52a7541c263bfa9d175d84b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oncodrivefml-2.5.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
c0446fa4fc5337c326d17a2e05773037ea6dda9280c0a769b43b0d94e2179992
|
|
BLAKE2b-256 checksum How to use checksums |
70b6c47f94d7d8be839d4f9e950c5347f4c412178a8faf6f753dbf53d37b1afe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | oncodrivefml-2.5.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 857.9 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b8eaa71dd38e4bb36144d05ed612fb1c8e64252d918cc8fa9736620491bd2e62
|
|
BLAKE2b-256 checksum How to use checksums |
3bee068429dd41d4407a6abf9059baa441c04ab31ada1704fcc5da1f86be6afc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oncodrivefml-2.5.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
cedac9fa11202853f5bb56370eb1865b40d1ab7f4a8244d7901e94a4fd93ba51
|
|
BLAKE2b-256 checksum How to use checksums |
727a159050f076ba8b1751620526265bf1fe7a13f16ff5eb40e8bbddbfb0d0f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | oncodrivefml-2.5.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 919.9 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0072435770eadb2e51ad49aa5bb7939728f861a27ac1de7efdeb617c4180a79a
|
|
BLAKE2b-256 checksum How to use checksums |
2e21bbcc4c7024c64f220eba6056465d50c0bd598bf21120669083248b2e53c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oncodrivefml-2.5.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
f48b37d4c764dbbbd0c790c70a1a2fa649242396960fd268d8cd1d9ca101c53e
|
|
BLAKE2b-256 checksum How to use checksums |
20662c2a2fe8d215c7a04aca9614c9b96f9ed2a49d9c48ce42f47d71e644f14e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | oncodrivefml-2.5.0-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 860.3 kB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3afe189a160efa5d8eec900c01d94b37571ccd290de56912d17904a9741d2a83
|
|
BLAKE2b-256 checksum How to use checksums |
69377cb53f95b76cbb2d505befbf76b726be68800a0d20878664179b8779ca05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oncodrivefml-2.5.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
551ca2568f5c16cb763214e5863ed2d37accf04ccbdbcff1d46c1581f6a7de7a
|
|
BLAKE2b-256 checksum How to use checksums |
be2f0f74f8551cb7034d6e626989e3f68bd2430338bb582611c9009e7dfee061
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Release files / oncodrivefml-2.5.0-cp38-cp38-macosx_11_0_arm64.whl
| Download URL | oncodrivefml-2.5.0-cp38-cp38-macosx_11_0_arm64.whl |
|---|---|
| Size | 800.1 kB |
| Tags | CPython 3.8 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6fbd963b04a46ee8023cbd7d17fb8c8e22cccb8716f63afc9367b089da3289f9
|
|
BLAKE2b-256 checksum How to use checksums |
554869d480bb78f6749d64bccb16b81735f7ecb815178e68ed5a4310f191b678
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.24
|
Security for oncodrivefml 2.5.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.