Last updated: 2022-07-20

Checks: 7 0

Knit directory: SISG2022_Association_Mapping/

This reproducible R Markdown analysis was created with workflowr (version 1.7.0). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.


Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.

Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.

The command set.seed(20220530) was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.

Great job! Recording the operating system, R version, and package versions is critical for reproducibility.

Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.

Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.

Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.

The results in this page were generated with repository version 490ce3e. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.

Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish or wflow_git_commit). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:


Ignored files:
    Ignored:    .DS_Store
    Ignored:    code/.Rhistory
    Ignored:    data/.DS_Store
    Ignored:    lectures/.DS_Store
    Ignored:    lectures/Figures/.DS_Store

Untracked files:
    Untracked:  data/Transferrin_height.bed

Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.


These are the previous versions of the repository in which changes were made to the R Markdown (analysis/Session07_practical.Rmd) and HTML (docs/Session07_practical.html) files. If you’ve configured a remote Git repository (see ?wflow_git_remote), click on the hyperlinks in the table below to view the files as they were in that past version.

File Version Author Date Message
Rmd 490ce3e Joelle Mbatchou 2022-07-20 fix typo
html 1612121 Joelle Mbatchou 2022-07-19 Build site.
Rmd a9da275 Joelle Mbatchou 2022-07-19 add q
html 32cd8c2 Joelle Mbatchou 2022-07-19 Build site.
Rmd 729353b Joelle Mbatchou 2022-07-19 use sim data in session 7 exercises
html 655cc83 Joelle Mbatchou 2022-07-18 Build site.
Rmd 01d32b1 Joelle Mbatchou 2022-07-18 cleanup edit
html d1d05e7 Joelle Mbatchou 2022-07-18 Build site.
Rmd c2458e1 Joelle Mbatchou 2022-07-18 add template R script
html e408daa Joelle Mbatchou 2022-07-18 Build site.
Rmd c1092d9 Joelle Mbatchou 2022-07-18 session 7 exercises

Before you begin:

  • Make sure that R is installed on your computer
  • For this lab, we will use the following R libraries:
require(data.table)
require(dplyr)
require(tidyr)
require(BEDMatrix)
require(SKAT)
require(ACAT)
require(ggplot2)

The R template to do the exercises is here.

Rare Variant Analysis

Introduction

We will look into a dataset collected on a quantitative phenotype which was first analyzed through GWAS and a signal was detected in chromosome 1. Let’s determine whether the signal is present when we focus on rare variation at the locus. In our analyses, we will define rare variants as those with \(MAF \leq 5\%\).

The file “rv_pheno.txt”” contains the phenotype measurements for a set of individuals and the file “rv_geno_chr1.bed” is a binary file in PLINK BED format with accompanying BIM and FAM files which contains the genotype data.

Exercises

Here are some things to try:

  1. Using PLINK, extract rare variants in a new PLINK BED file. (Hint: use options --max-maf to select rare variants and --maj-ref force so that the minor allele is the effect allele)

  2. Load the data in R:

  • Read in the SNPs using R function BEDMatrix() (hint: use option simple_names = TRUE to easily filter by sample IID later)
  • Load the phenotype data from rv_pheno.txt
  • Keep only samples who are present both in the genotype as well as phenotype data and who don’t have missing values for the phenotype
  1. Examine the genotype data:
  • Compute the minor allele frequency (MAF) for each SNP and plot histogram. (hint: use na.rm=TRUE when calling mean())
  • Check for missing values
  1. Run the single variant association tests in PLINK (only for the extracted variants).
  • Compute the minimum p-value across SNPs and apply Bonferroni correction for the multiple testing (hint: take \(\min(1, p\cdot K)\), where \(p\) is the minimum p-value and \(K\) is the number of tests). Is anything significant after adjusting for multiple testing?
  • Make a volcano plot (i.e. log10 p-values vs effect sizes). Which of the Burden/SKAT/ACAT tests do you expect will give us most power?

Reminder: The PLINK2 command would look like

plink2 --bfile <BED_file_with_extracted_SNPs> --pheno rv_pheno.txt --pheno-name <pheno_name> --glm allow-no-covars --out <output_prefix>
  1. We will first compare three collapsing/burden approaches:
  • CAST (Binary collapsing approach): for each individual, count where they have a rare allele at any of the sites
  • MZ Test/GRANVIL (Count based collapsing): for each individual, count the total number of sites where a rare allele is present
  • Weighted burden test: for each individual, take a weighted count of the rare alleles across sites (for the weights, use weights <- dbeta(MAF, 1, 25))

For each approach, first generate the burden scores vector then test it for association with the phenotype using lm() R function.

  1. Now use SKAT to test for an association. The basic command would look like
# fit null model (no covariates)
skat.null <- SKAT_Null_Model( <phenotype_vector> ~ 1 , out_type = "C")
# Run SKAT association test (returns a list - p-value is in `$p.value`)
SKAT( <genotype_matrix>, skat.null )
  1. Run the omnibus SKAT, but consider setting \(\rho\) (i.e.r.corr) to 0 and then 1.
  • Compare the results to using the CAST,MZ/GRANVIL and Weighted burden collapsing approaches in Question 5 as well as SKAT in Question 6. What tests do these \(\rho\) values correspond to? The basic command would look like
# Run SKATO association test specifying rho
SKAT( <genotype_matrix>, skat.null, r.corr = <rho_value>)
  1. Now the omnibus version of SKAT, but use the “optimal.adj” approach which searches across a range of rho values. The basic command would look like
# Run SKATO association test using grid of rho values
SKAT( <genotype_matrix>, skat.null, method="optimal.adj")
  1. Run ACATV on the single variant p-values. The basic command would look like
# `weights` vector is from Qesution 5
acat.weights <- weights * weights * MAF * (1 - MAF)
ACAT( <pvalues>, weights = acat.weights)
  1. Run ACATO combining the SKAT and BURDEN p-values (from Question 7) with the ACATV p-value (from Question 9). The basic command would look like
ACAT( c(<pvalue_SKAT>, <pvalue_Burden>, <pvalue_ACATV>))

sessionInfo()
R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS  10.16

Matrix products: default
BLAS:   /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] workflowr_1.7.0

loaded via a namespace (and not attached):
 [1] Rcpp_1.0.8.3     bslib_0.3.1      jquerylib_0.1.4  compiler_3.6.1  
 [5] pillar_1.7.0     later_1.3.0      git2r_0.30.1     tools_3.6.1     
 [9] getPass_0.2-2    digest_0.6.25    jsonlite_1.7.2   evaluate_0.15   
[13] tibble_2.1.3     lifecycle_1.0.1  pkgconfig_2.0.3  rlang_1.0.4     
[17] cli_3.1.1        rstudioapi_0.13  yaml_2.2.1       xfun_0.31       
[21] fastmap_1.1.0    httr_1.4.3       stringr_1.4.0    knitr_1.39      
[25] sass_0.4.0       fs_1.5.2         vctrs_0.3.8      rprojroot_2.0.3 
[29] glue_1.6.1       R6_2.4.1         processx_3.5.3   fansi_0.4.1     
[33] rmarkdown_2.14   callr_3.7.0      magrittr_1.5     whisker_0.4     
[37] ps_1.7.0         promises_1.2.0.1 htmltools_0.5.2  ellipsis_0.3.2  
[41] httpuv_1.6.5     utf8_1.1.4       stringi_1.4.6    crayon_1.3.4