CoCalc Shared Files32_Analysis_of_Genetic_Variation_II / 32_Analysis_of_Genetic_Variation_II_inclass.htmlOpen in CoCalc with one click!
Author: Cuauhtemoc Sandoval
Views : 31
Description: Jupyter html version of 32_Analysis_of_Genetic_Variation_II/32_Analysis_of_Genetic_Variation_II_inclass.ipynb
32_Analysis_of_Genetic_Variation_II_inclass

Analysis of Genetic Variation - II

Table of contents

  1. Processing of new data set
  2. Multi-dimensional scaling analysis
  3. Running logistic regression-based association

1. Processing of new data set

For this module, we are going to go through the scenario where your PI gives you a dataset and tells that you have to perform the standard filtering steps, analyze it, and return the results (without actually telling you what the dataset represents). Luckily, we learned many of the relevant commands in the first genetic variation module, so you have all the tools you need to impress your demanding PI.

If you look in the '~/32_Analysis_of_Genetic_Variation_II_data/' directory (which is not in this assigment folder but should be in your home directory), you will see three files with extensions that should look somewhat familiar to you from the last class:

  1. malmo_v4.bed: a binary ped file containing the genotypes for each subject. Note that this is different than the bed files that we have seen before!
  2. malmo_v4.bim: an extended MAP file containing allele name information corresponding to the genotypes in the bed file
  3. malmo_v4.fam: the first six columns of the original .ped file, corresponding to the pedigree and phenotype information for each subject

You will also see a file called malmo_v4_mds.mds, which we will investigate in parts 2 and 3.

First, let's run the basic PLINK command to look at this data, and send the output to 'plink_output/validation' within this assignment folder. Note that to use the binary file, you have to use the '--bfile' flag instead of the '--file' flag.

Record the command you ran:

$ plink --bfile ../32_Analysis_of_Genetic_Variation_II_data/malmo_v4 --out ./plink_output/validation --noweb

How many SNPs are in this dataset?

92292 SNPs.

How many cases and controls are in this dataset?

1048 cases, 1111 controls.

Now let's perform similar filtering to what we did for the first module: add a MAF threshold of 0.01, a SNP genotyping rate of 0.05, and missingness per individual/sample of 0.1. In addition to these filters, we will also add a filter to exclude SNPs that significantly diverge from Hardy-Weinberg equilibrium, which is meant to identify SNPs that are under specific evolutionary forces and may therefore not be appropriate to include in a case/control association study. Look through the PLINK thresholding page to find the flag for filtering by HWE. What is that flag?

--hwe N

Now, let's filter out SNPs that significantly deviate from HWE with a p-value of 0.001 or less, in addition to the other filters described above. Record the code you ran here, and send the output to 'plink_output/filtering' in this directory:

$ plink --maf 0.01 --geno 0.05 --mind 0.1 --hwe .001 --bfile ../32_Analysis_of_Genetic_Variation_II_data/malmo_v4 --missing --out ./plink_output/filtering --noweb

How many individuals were removed for low genotyping?

159 individuals.

How many SNPs were filtered out for diverging from HWE?

8232 SNPs were removed.

How many SNPs failed the missingness test?

1738 SNPs failed missingness test.

How many SNPs failed the MAF test?

13571 SNPs failed frequency test

How many SNPs passed all the filtering?

69165 SNPs passed all the filtering.

How many cases and controls passed filtering?

1000 cases and 1000 controls.

2. Multi-dimensional scaling analysis

A very common and important analysis in genetic studies is to consider the population stratification of the sample: because different ancestries/populations have different genetic architectures, comparing people without consideration of which population they come from can lead to false results, where a genetic signal may seem to be associated with a trait but really be due to differences between the case and control populations. The standard way to analyze this stratification is to calculate the genotype-based pairwise distances between each individual and each other individual, perform multi-dimensional scaling on these distances, which provides a way to make a 2D plot of the similarity of the individuals in the dataset, and cluster individuals based on this information to account for different populations.

You can read this PLINK page that describes approaches for understanding population stratification. We have generated a multidimensional scaling file for you called 'malmo_v4_mds.mds', also in the ~/32_Analysis_of_Genetic_Variation_II_data/ directory. Read through the linked PLINK page to find the flags that you would use to generate an MDS file with 3 dimensions (but do not run this command, as it takes a long time!):

T$ plink --bfile ../32_Analysis_of_Genetic_Variation_II_data/malmo_v4_mds.mds --read-genome plink.genome --cluster --mds-plot 3

Next, download this MDS file, read it into R (noting that there is a header), and plot the first two dimensions against each other (the 3rd and 4th columns of the data file), and save the plot into the images/ folder of this assignment.

Do you see anything suggesting that there is population stratification in this sample?

The plot suggests that there is indeed population stratification in the sample between, as the first two dimsensions seem to show 2 distinct populations stratified within the sample.

3. Running logistic regression-based association

Given that we have seen population stratification, the question of how to account for this in our association test still remains. Instead of using the basic '--assoc' flag to do our association test, we now have to use a more sophisticated flag, which is the '--logistic' flag. This tells PLINK that we want to run a logistic regression, which is one way to predict a categorical value (i.e. the case or control status of each individual) while taking genotype weights as well as other covariates, in this case the population clusters, into account. In PLINK, we can specify the MDS file as a covariate for the logistic regression model to account for using the '--covar' flag with the malmo_v3_indcln.mds file as the argument.

We will also use two new flags that we haven't seen before: to adjust for multiple testing and sort the output by correct signifiance, we use the '--adjust' flag, and to generate 95% confidence intervals around the estimated parameters, we use the '--ci 0.95' flag.

Write the command with all the filters that we used before plus the --logistic flag, the --covar flag with the MDS file as the argument, and the two flags described above to run this logistic association test, and send the output to plink_output/filtering_and_logistic:

$ plink --bfile ../32_Analysis_of_Genetic_Variation_II_data/malmo_v4 --logistic --covar ../32_Analysis_of_Genetic_Variation_II_data/malmo_v4_mds.mds --adjust --ci 0.95 --out ./plink_output/filtering_and_logistic --noweb

This may take a few minutes, but now we have our logistic regression results in two files: plink_output/filtering_and_logistic.assoc.logistic, which contains the logistic regression and the 95% confidence intervals for the odds ratios of each SNP, and plink_output/filtering_and_logistic.assoc.logistic.adjusted, which contains the SNPs sorted by their adjusted p-values. Give the command to look at the first 30 lines of the adjusted file:

$ head -30 filtering_and_logistic.assoc.logistic.adjusted

By looking at the relatively conservative Bonferroni corrected p-values (the BONF column), how many SNPs are significant at a p-value cutoff of 0.05?

10 SNPs.

Now look at the less conservative Benjamini-Hochberg computation of the false discovery rate, the 'FDR_BH' column in the data file. How many SNPs are significant at a cutoff of 0.05 false discovery?

19 SNPs.

The two output files contain different information, including the actual position of each SNP in filtering_and_logistic.assoc.logistic. One important analysis that we should do is to figure out if we have many different and independent significant signals or if there are some significant SNPs that are close to each other, suggesting that they are in linkage disequilibrium and may be tagging the same causal mechanism. Since we don't have too many significant SNPs, we can figure this out by simply grepping for the top Bonferroni SNPs in filtering_and_logistic.assoc.logistic and looking at where they reside. Note that each SNP has 4 lines in this file, for each of four tests: additive, which accounts for all the covariates, and one test for each of the three MDS covariates.

Fill in the following cell with the grep code you ran for each SNP and the corresponding output (you only need to include the first line of the result). We have filled out the first one for you including the header line:

head1plinkoutput/filteringandlogistic.assoc.logistic;grep"rs2244797"plinkoutput/filteringandlogistic.assoc.logisticCHRSNPBPA1TESTNMISSORSEL95U95STATP20rs2244797368256031ADD19810.62450.075230.53890.72376.2583.891e10 head -1 plink_output/filtering_and_logistic.assoc.logistic; grep "rs2244797" plink_output/filtering_and_logistic.assoc.logistic CHR SNP BP A1 TEST NMISS OR SE L95 U95 STAT P 20 rs2244797 36825603 1 ADD 1981 0.6245 0.07523 0.5389 0.7237 -6.258 3.891e-10

By 'clumping' nearby SNPs together based on their positions (the third column here), how many distinct association signals do you think there are?

What are the general odds ratios for each of the distinct signals you identified? Are they in the same direction, and can you generally interpret what these values represent? How do these correspond to the 'STAT' column in the logistic output file?

Finally, go on the genome browser and check these regions of associations, making sure to use the hg18 assembly; what genes do you see in these regions and can you give any general interpretation given that we haven't told you what our actual phenotype is?

Now you can give these results to your PI, who will surely be impressed with your knowledge of the somewhat esoteric art of running PLINK commands!