MetaXcan is a set of tools to integrate genomic information of biological mechanisms with complex traits. Almost all of the software here is command-line based.
This software has been recently migrated to python 3 as python 2 has been sunset.
Here you can find the latest implementation of PrediXcan: PrediXcan.py. This uses individual-level genotype and phenotype, along a mechanism's prediction model (e.g. models predicting expression or splicing quantification), to compute associations between omic features and a complex trait.
S-PrediXcan is an extension that infers PrediXcan's results using only summary statistics, implemented in SPrediXcan.py. A manuscript describing S-PrediXcan and the MetaXcan framework with an application can be found S-PrediXcan.
MultiXcan (MulTiXcan.py) and S-MultiXcan (SMulTiXcan.py) compute omic associations, integrating measurements across tissues while factoring correlation. For example, if you have prediction models, each trained on different regions of the brain, MulTiXcan will combine the information across all experiments. This is effectively a meta-analysis across tissues, where each tissue is an experiment and we explictly account for correlation.
The software is developed and tested in Linux and Mac OS environments. The main S-PrediXcan script is also supported in Windows.
To run S-PrediXcan, you need Python 3.5 or higher, with the following libraries:
- numpy (>=1.11.1)
- scipy (>=0.18.1)
- pandas (>=0.18.1)
- sqlalchemy is needed at some unit tests.
To run PrediXcan Associations and MulTiXcan, you also need:
- patsy (>=0.5.0)
- statsmodels (>=0.8.0)
- h5py (>=2.7.1)
- h5py-cache (>=1.0.0) *Now folded into h5py
To run prediction of biological mechanisms on individual-level data, you will also need:
R with ggplot and dplyr is needed for some optional statistics and charts.
We recommend a tool like Conda to set up a working environment for MetaXcan. Tools like pyenv also work, but the bgen-reader dependency currently takes some effort to get going on pyenv.
A quick-and-dirty solution to install the basic requirements is using Miniconda and the file software/conda_env.yaml
in this repository to create a working environment.
conda env create -f /path/to/this/repo/software/conda_env.yaml
conda activate imlabtoolsWe make available several transcriptome predictione models and LD references here.
These files should be enough for running SPrediXcan.py, MulTiXcan.py and SMulTiXcan.py on practically any GWAS study.
We highly recommend MASHR models therein, as they are parsimonious and biologically-informed, using fine-mapped variants and cross-tissue QTL patterns.
In the following we use gene recurrently to refer to the prediction model of a genetic feature,
but it can stand for other units such as prediction of an intron's quantification.
we provide a end-to-end tutorial, for integrating GWAS summary statistics on the latest release of GTEx models.
software folder contains an implementation of S-PrediXcan's method and associated tools. The following scripts from that folder constitute different components in the MetaXcan pipeline:
SPrediXcan.py
PrediXcan.py
MulTiXcan.py
SMulTiXcan.py, although SPrediXcan.py is the most widely applicable. SPrediXcan.py script contains the current implementation of S-PrediXcan.
MulTiXcan.py and SMulTiXcan.py are the multiple-tissue methods.
MultiXcan.py uses as input the predicted levels generated by PrediXcan.py.
The rest of the scripts in software folder are python packaging support scripts, and convenience wrappers such as the GUI.
Subfolder software/metax contains the bulk of Metaxcan's logic, implemented as a python module.
S-PrediXcan will calculate the gene-level association results from GWAS summary statistics. It supports most GWAS formats by accepting command line argument specifying data columns. Some precalculated data is needed, that must be set up prior to S-PrediXcan execution.
The gist of S-PrediXcan's input is:
- A Transcriptome Prediction Model database (an example is here)
- A file with the covariance matrices of the SNPs within each gene model (such as this one)
- GWAS results (such as these, which were computed on a randomly generated phenotype). GWAS results can belong to a single file or be split into multiple ones (i.e. split by chromosome). You can specify the necessary columns via command line arguments (i.e. which column holds snps, which holds p-values, etc)
You can use precalculated databases, or generate new ones with tools available in PredictDB repository. GTEx-based tissues and 1000 Genomes covariances precalculated data can be found here.
(Please refer to /software/Readme.md for more detailed information)
S-PrediXcan supports a large number of input GWAS formats through command line arguments. By specifying the appropriate input file column name, S-PrediXcan will analize the file without extra need for input conversion. Input GWAS files can be plain text files or gzip-compressed.
For example, you can specify an effect allele column and a standard error column, or a pvalue column and an odds ratio column, or only a GWAS zscore column. S-PrediXcan will try to use the following (in that order) if available from the command line arguments and input GWAS file:
- use a z-score column if available from the arguments and input file;
- use a p-value column and either effect, odd ratio or direction column;
- use effect size (or odd ratio) and standard error columns if available.
Check the Github's ' wiki for those that work best for your data, and interpreting the results. For example, if your GWAS has p-values that are too small (i.e 1e-350), then you should avoid specifying a p-value column because numerical problems might arise; you should use effect size and standard error instead.
PrediXcan supports three input file formats:
- vcf
- bgen
- internal "dosage format".
Associations are output as a tab-separated file.
Predicted levels can be output as both text files or HDF5 files. HDF5 files allow a more efficient computation of MultiXcan, as only data for a single gene/inton/whaever across all tissues can be loaded at a time.
The following example assumes that you have python 3.5 (or higher), numpy, and scipy installed.
- Clone this repository.
$ git clone https://github.com/hakyimlab/MetaXcan- Go to the software folder.
$ cd MetaXcan/software- Download example data.
This may take a few minutes depending on your connection: it has to download approximately 200Mb worth of data. Downloaded data will include an appropiate Transcriptome Model Database, a GWAS/Meta Analysis summary statistics, and SNP covariance matrices.
Extract it with:
tar -xzvpf sample_data.tar.gz- Run the High-Level S-PrediXcan Script
./SPrediXcan.py \
--model_db_path data/DGN-WB_0.5.db \
--covariance data/covariance.DGN-WB_0.5.txt.gz \
--gwas_folder data/GWAS \
--gwas_file_pattern ".*gz" \
--snp_column SNP \
--effect_allele_column A1 \
--non_effect_allele_column A2 \
--beta_column BETA \
--pvalue_column P \
--output_file results/test.csvThis should take less than a minute on a 3GHZ computer. For the full specification of command line parameters, you can check the wiki.
The example command parameters mean:
--model_db_pathPath to tissue transriptome model--covariancePath to file containing covariance information. This covariance should have information related to the tissue transcriptome model.--gwas_folderFolder containing GWAS summary statistics data.--gwas_file_patternThis option allows the program to select which files from the input to use based on their name. ...This allows to ignore several support files that might be generated at your GWAS analysis, such as plink logs.--snp_columnArgument with the name of the column containing the RSIDs.--effect_allele_columnArgument with the name of the column containing the effect allele (i.e. the one being regressed on).--non_effect_allele_columnArgument with the name of the column containing the non effect allele.--beta_columnTells the program the name of a column containing -phenotype beta data for each SNP- in the input GWAS files.--pvalue_columnTells the program the name of a column containing -PValue for each SNP- in the input GWAS files.--output_filePath where results will be saved to.
Its output is a CSV file that looks like:
gene,gene_name,zscore,effect_size,pvalue,var_g,pred_perf_r2,pred_perf_pval,pred_perf_qval,n_snps_used,n_snps_in_cov,n_snps_in_model
ENSG00000150938,CRIM1,4.190697619877402,0.7381499095142079,2.7809807629839122e-05,0.09833448081630237,0.13320775358,1.97496173512e-30,7.47907447189e-30,37,37,37
...
Where each row is a gene's association result:
gene: a gene's id: as listed in the Tissue Transcriptome model. Ensemble Id for most gene model releases. Can also be a intron's id for splicing model releases.gene_name: gene name as listed by the Transcriptome Model, typically HUGO for a gene. It can also be an intron's id.zscore: S-PrediXcan's association result for the gene, typically HUGO for a gene.effect_size: S-PrediXcan's association effect size for the gene. Can only be computed whenbetafrom the GWAS is used.pvalue: P-value of the aforementioned statistic.pred_perf_r2: (cross-validated) R2 of tissue model's correlation to gene's measured transcriptome (prediction performance). Not all model families have this (e.g. MASHR).pred_perf_pval: pval of tissue model's correlation to gene's measured transcriptome (prediction performance). Not all model families have this (e.g. MASHR).pred_perf_qval: qval of tissue model's correlation to gene's measured transcriptome (prediction performance). Not all model families have this (e.g. MASHR).n_snps_used: number of snps from GWAS that got used in S-PrediXcan analysisn_snps_in_cov: number of snps in the covariance matrixn_snps_in_model: number of snps in the modelvar_g: variance of the gene expression, calculated asW' * G * W(whereWis the vector of SNP weights in a gene's model,W'is its transpose, andGis the covariance matrix)
If --additional_output is used when running S-PrediXcan, you'll get two additional columns:
best_gwas_p: the highest p-value from GWAS snps used in this modellargest_weight: the largest (absolute value) weight in this model
Please see the following article in the wiki.
Run SMultiXcan.py --help to see arguments and options.
Output is a tab-separated text file with the following columns:
gene: a gene's id: as listed in the Tissue Transcriptome model. Ensemble Id for most gene model releases. Can also be a intron's id for splicing model releases.gene_name: gene name as listed by the Transcriptome Model, typically HUGO for a gene. It can also be an intron's id.pvalue: significance p-value of S-MultiXcan associationn: number of "tissues" available for this genen_indep: number of independent components of variation kept among the tissues' predictions. (Synthetic independent tissues)p_i_best: best p-value of single-tissue S-PrediXcan association.t_i_best: name of best single-tissue S-PrediXcan association.p_i_worst: worst p-value of single-tissue S-PrediXcan association.t_i_worst: name of worst single-tissue S-PrediXcan association.eigen_max: In the SVD decomposition of predicted expression correlation: eigenvalue (variance explained) of the top independent componenteigen_min: In the SVD decomposition of predicted expression correlation: eigenvalue (variance explained) of the last independent componenteigen_min_kept: In the SVD decomposition of predicted expression correlation: eigenvalue (variance explained) of the smalles independent component that was kept.z_min: minimum z-score among single-tissue S-Predican associations.z_max: maximum z-score among single-tissue S-Predican associations.z_mean: mean z-score among single-tissue S-Predican associations.z_sd: standard deviation of the mean z-score among single-tissue S-Predican associations.tmi: trace ofT * T', whereTis correlation of predicted expression levels for different tissues multiplied by its SVD pseudo-inverse. It is an estimate for number of indepent components of variation in predicted expresison across tissues (typically close ton_indep)status: If there was any error in the computation, it is stated here
You also have the option of installing the MetaXcan package to your python distribution. This will make the metax library available for development, and install on your system path the main MetaXcan scripts.
You can install it from the software folder with:
# ordinary install
$ python setup.py installAlternatively, if you are going to modify the sources, the following may be more convenient:
# developer mode instalation
python setup.py developPIP support coming soon-ish.
Issues and questions can be raised at this repository's issue tracker.
There is also a Google Group mail list for general discussion, feature requests, etc. Join if you want to be notified of new releases, feature sets and important news concerning this software.
You can check here for the release history.
Transcriptome Models are a key component of PrediXcan and S-PrediXcan input. As models are improved, sometimes the format of these databases needs be changed too. We only provide support for the very latest databases; if a user updates their repository clone to the latest version and MetaXcan complains about the transcriptome weight dbs, please check if new databases have been published here.
For the time being, the only way to use old transcriptome models is to use older versions of MetaXcan.
Older versions of MetaXcan have a MetaXcan.py script, when it meant to be an entry point to all MetaXcan tools, but it has since been renamed SPrediXcan.py.
Check software folder in this repository if you want to learn about more general or advanced usages of S-PrediXcan, or MulTiXcan and SMulTiXcan.
Check out the Wiki for exhaustive usage information.
The code lies at
/softwareNew release and features coming soon!
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent