Using --Logistic --Interaction --Condition To Search For Epistasis In Plink, And Vif Issues
1
2
Entering edit mode
12.6 years ago

I've been investigating ways of looking for epistasis in GWAS data, with the intention of looking for interactions with a specific SNP (hence the --condition option used above). From my tests so far, the above options appear to replicate results fairly closely to methods I can use in R, and also the --epistasis module in PLINK, while still allowing me to apply additional covariates (not allowed with --epistasis) and to easily carry out on a genome wide scale (my approach in R was on a per-interaction basis).

My question two-fold. Firstly, is this combination of commands appropriate as a replacement for --epistasis? I'm effectively just doing the same kind of logistic regression after all from what I can see.

Secondly, in order to get anything other than NA's throughout the results file, I had to raise the VIF using --vif, as recommended in the PLINK manual here. However simply raising it to a VIF of 100 didn't help, trying it at --vif 1000 finally gave me output (though towards the end of the file I still got many NAs). How does applying the VIF modification affect my results? Are the results still valid? Will raising the VIF even further get rid of remaining NAs? Would that even be necessary? (As the top results I get from what I have so far seem to make sense in context)

plink • 3.9k views
ADD COMMENT
1
Entering edit mode
12.2 years ago
ff.cc.cc ★ 1.3k

About the first point I agree with your conclusion: the estimated interaction parameters should be equal. The only limiting factor using --condition is that one of the two interactant snps is always the same (but your true advantage is the use of the covariates)

Secondly I am not expert with the tuning of the --vif param, but I would suggest (maybe you just did...?) to prune your data on a linkage disequilibrium basis, so to reduce redundancy of signals and lowering the level of similarity between markers.

hope this help

ADD COMMENT

Login before adding your answer.

Traffic: 2932 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6