Co-Regulation Predictor
Transcription of a gene is a highly regulated process with multiple Transcription Factors (TF) working in coordination with each other. CoRegTor (which stands for CO-REGulation predicTOR) is a tool to predict potential coregulators of a specific target gene using gene expression data. It can also be used to find frequently occurring co-regulators within the gene expression data.
Installation
pip install coregtor
Documentation
The documentation is available here
Tutorial to use the python package
Tutorial to use the bulk pipeline
Usage
Data required
The 2 main inputs required are:
- The gene expression data where rows are samples and columns are genes.
- A list transcription factors. Their names must match with the names of the genes name columns in the gene expression data. For humans, TF list is available here. Additionally, you can also include the genes associated with the GO term transcription coregulator activity. Let
Please see the API doc for more details on the parameters.
1 maintainer
Metadata
1 maintainer
Release files for coregtor 0.5.1
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 |
|---|---|---|---|---|
| coregtor-0.5.1.tar.gz | 33.5 kB | With provenance | Details for coregtor-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| coregtor-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for coregtor-0.5.1-py3-none-any.whl |
Total release size: 71.6 kB
Release files / coregtor-0.5.1.tar.gz
| Download URL | coregtor-0.5.1.tar.gz |
|---|---|
| Size | 33.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6415dbae57ad9e9dcef17f7a500033eaacd88058e5218545acc3c99c4f0a4e59
|
|
BLAKE2b-256 checksum How to use checksums |
108359c07ed0e139c4b719c8595ed06eb9c796828867f7970c06565dc201ab8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / coregtor-0.5.1-py3-none-any.whl
| Download URL | coregtor-0.5.1-py3-none-any.whl |
|---|---|
| Size | 38.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f648fc6e25cdf1ec8dd601a5163988ec7f78545f6e979337e72c772b7971ac0
|
|
BLAKE2b-256 checksum How to use checksums |
8d6b1db5ec88ef5060fad845c3a8a89b5211d966e21e06eb542f9e6296284a69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for coregtor 0.5.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for coregtor-0.5.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA 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.
