A package to benchmark pre-trained models on downstream gene-related tasks.
The package adopts a framework that allows comparison of models using multiple input types by focusing on the learned embeddings the model provides for each entity. This allows comparing models trained on text, proteins, transcriptomics, or any other modality.
The repository is divided into the following sections:
-
gene_benchmark: The package itself, containing the scripts for extracting textual descriptions from NCBI, encoding textual descriptions and evaluation of model performance.
-
notebooks: Notebooks for creating the results figures and package usage examples.
-
scripts: Scripts for description extraction, encoding, task creation and execution.
-
tasks: The default directory that will be populated with all the tasks after running the task creation script.
In depth explanation on each of the packages components can be found in the gene_benchmark
directory.
Using a virtual environment for all commands in this guide is strongly recommended. Both conda and vanilla venv environments are supported.
# create a conda enviornment "gene_benchmark" with Python version 3.11
conda create -n gene_benchmark python=3.11
# activate the enviornment before installing new packages
conda activate gene_benchmark
The following command will install the repository as a Python package, and also attempt to install dependencies speficied in the setup.py file or the pyproject.toml. Note that the command does not clone the repositpry.
# assuming you have an SSH key set up on GitHub
# this
pip install "git+ssh://github.com/BiomedSciAI/gene-benchmark.git"
# Change directory to the root of the cloned repository
cd gene-benchmark
# install from the local directory
pip install -e .
# Clone the cloned repository
git clone git@github.com:BiomedSciAI/gene-benchmark.git
# Change directory to the root of the cloned repository
cd gene-benchmark
pip install --upgrade pre-commit
# install from the local directory
pip install -e .
pre-commit install
To evaluate your model on the tasks a few basic steps need to be done:
- Create the tasks: To download the files containing the tasks, run the following commands in your terminal from the root directory. Note that each task dataset has its own license, which is separate from the license of this package.
python scripts/tasks_retrieval/gene2gene_task_creation.py --allow-downloads True
python scripts/tasks_retrieval/Genecorpus_tasks_creation.py --allow-downloads True
python scripts/tasks_retrieval/HLA_task_creation.py --allow-downloads True
python scripts/tasks_retrieval/HPA_tasks_creation.py --allow-downloads True
python scripts/tasks_retrieval/humantfs_task_creation.py --allow-downloads True
python scripts/tasks_retrieval/Reactome_tasks_creation.py --allow-downloads True
python scripts/tasks_retrieval/uniprot_keyword_tasks_creation.py --allow-downloads True
Now your tasks directory should be populated with subdirectories with the tasks names. Each subdirectory holds two .csv files, one with the gene symbols (entities.csv) and one with the labels (outcomes.csv). The shape of these csv files will be determined based on the task type. For example, for the multi class tasks, the outcomes will be a 2d matrix.
- Create your task yaml: The script for running the tasks can receive either the task names themselves or a .yaml file containing the list of task names you wish to run. If you choose to create a .yaml file with the task names, create a separate file for each task type. For example for the binary tasks:
- TF vs non-TF
- long vs short range TF
- bivalent vs non-methylated
- Lys4-only-methylated vs non-methylated
- dosage sensitive vs insensitive TF
- Gene2Gene
- CCD Transcript
- CCD Protein
- N1 network
- N1 targets
- HLA class I vs class II
The example task configs can be found in task_configs
- Create the model config file: This config file will hold the path to your models embeddings and the name you wish to use for your model. The structure of the file:
encoder:
class_name: PreComputedEncoder
class_args:
encoder_model_name: "/path/to/your/embeddings/my_models_embeddings.csv"
model_name: my_model_name
Note that the script expects the embedding csv file to have a 'symbol' column with the gene symbols, this will be set as the index.
Each task type (binary, categorical or multi-label) will be run separately. For example, for running the binary tasks the command is:
python scripts/run_task.py -t /path/to/task/yaml/base_binary.yaml -tf /tasks -m /path/to/model/config/model.yaml --output-file-name binary_tasks.csv
Note:
-
For the other task types (categorical, regression or multi labe) you need to add
-s category/regression/multi
-
When you are running the tasks on multiple models, and you would like them to be comparable, you can add a
excluded-symbols-file
input. This needs to be a path to a yaml file containing a list of gene names you would like to exclude. -
To avoid getting errors during the cross validation due to class imbalance, you can add a threshold for the classes
"-th"
(for multi label)or"-cth"
(for categorical)