-
Notifications
You must be signed in to change notification settings - Fork 29
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
Specify covariates file and PCA #12
Comments
Hi Lili, |
So indeed it is right now unfortunately only possible to either add your covariates manually with the covariate file or let vcf2gwas extract the PCs from the VCF file and use them as covariates (as shown in the Manual). Additionally using the PCA based correction instead of GEMMA's kinship matrix of course only works when you are using the linear mixed model (see here). |
Hi Gautam and Frank, Thank you very much for the answers. As I understood, kinship matrix implemented in GEMMA calculates relatedness between individuals and is different from population structure. Therefore, if one wants to correct for population structure on top of relatedness when using a linear mixed model, one can either let vcf2gwas calculates and subtract top PCs or provide a covariate file with top PCs. In the first scenario, does vcf2gwas calculate PCA based on all SNPs in the genotype file, or will vcf2gwas calculates PCs on independent SNPs on autosomal chromosomes only? I'm new to population genetics so pardon me if I ask stupid questions. Best, |
Hi Lili, |
Hi Gautam, Thanks a lot for the fast reply. Since kinship matrix captures population struture, does that mean further adjusting for population strucutre by including top N number of PCs is not needed? Best, |
Hi Lili, |
Hi Frank,
Thank you for creating this streamlined tool for performing GWAS analysis. Regarding covariates, if I want to correct for e.g. age, sex and population structure, how can I do this? Can I specify a covariate file AND subtract top PCs from PCA of the vcf file? Thanks a lot for your help.
Best,
Lili
The text was updated successfully, but these errors were encountered: