Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using the Gtexv8- mashr model #89

Closed
gpwhiz opened this issue Feb 5, 2020 · 1 comment
Closed

Using the Gtexv8- mashr model #89

gpwhiz opened this issue Feb 5, 2020 · 1 comment

Comments

@gpwhiz
Copy link

gpwhiz commented Feb 5, 2020

Hi,
Thank you for the updated version.
I have used the GTEX v8 mashr models. I did the GWAS harmonization using the first (or the recommended) method. I didn't impute and ran the MetaXcan.py.
In the output file, three columns related to prediction - pred_* had all NAs.
Is there a value(parameter) I should have used to get these?

The following is my script and parameters
python2 MetaXcan/software/MetaXcan.py
--gwas_file mygwas-harmonize.txt.gz
--snp_column panel_variant_id --effect_allele_column effect_allele --non_effect_allele_column non_effect_allele --zscore_column zscore
--model_db_path data/models/eqtl/mashr/mashr_Whole_Blood.db
--covariance data/models/eqtl/mashr/mashr_Whole_Blood.txt.gz
--keep_non_rsid --additional_output --model_db_snp_key varID
--throw
--output_file mygwas-mashr-GTexV8_Whole_Blood.csv

Thank you for helping.

@Heroico
Copy link
Collaborator

Heroico commented Feb 7, 2020

Hi there,

The pred* columns do not apply to MASHR models, therefore it is expected for them to be NA.

The pred* columns detail cross-validated prediction performance, a statistic defined only on Elastic Net models. The MASHR models have no prediction performance measure.

BEst,

alvaro

@Heroico Heroico closed this as completed Feb 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants