Last updated: 2019-08-21

Checks: 1 1

Knit directory: Comparative_eQTL/analysis/

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


The R Markdown file has unstaged changes. To know which version of the R Markdown file created these results, you’ll want to first commit it to the Git repo. If you’re still working on the analysis, you can ignore this warning. When you’re finished, you can run wflow_publish to commit the R Markdown file and build the HTML.

Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility. The version displayed above was the version of the Git repository at the time these results were generated.

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:    .Rhistory
    Ignored:    .Rproj.user/
    Ignored:    analysis/.DS_Store
    Ignored:    analysis/20190521_eQTL_CrossSpeciesEnrichment_cache/
    Ignored:    analysis_temp/.DS_Store
    Ignored:    code/.DS_Store
    Ignored:    code/snakemake_workflow/.DS_Store
    Ignored:    data/.DS_Store
    Ignored:    data/PastAnalysesDataToKeep/.DS_Store
    Ignored:    docs/.DS_Store
    Ignored:    docs/assets/.DS_Store

Unstaged changes:
    Modified:   analysis/index.Rmd

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 R Markdown and HTML files. If you’ve configured a remote Git repository (see ?wflow_git_remote), click on the hyperlinks in the table below to view them.

File Version Author Date Message
Rmd b62b089 Benjmain Fair 2019-08-21 update site
html b62b089 Benjmain Fair 2019-08-21 update site
Rmd fdbae12 Benjmain Fair 2019-08-14 updates
Rmd 641b1d9 Benjmain Fair 2019-07-11 update site
html 641b1d9 Benjmain Fair 2019-07-11 update site
Rmd 34e6b4f Benjmain Fair 2019-07-11 update site
html 34e6b4f Benjmain Fair 2019-07-11 update site
Rmd c3dbe5a Benjmain Fair 2019-06-19 update site
html c3dbe5a Benjmain Fair 2019-06-19 update site
Rmd 22eda3a Benjmain Fair 2019-06-12 update site
html 22eda3a Benjmain Fair 2019-06-12 update site
Rmd 7ef6fe2 Benjmain Fair 2019-06-11 update site
html 7ef6fe2 Benjmain Fair 2019-06-11 update site
html 8ab5bbf Benjmain Fair 2019-05-02 update site
Rmd f47ec35 Benjmain Fair 2019-04-25 updated site
html f47ec35 Benjmain Fair 2019-04-25 updated site
Rmd e592335 Benjmain Fair 2019-04-03 build site
html e592335 Benjmain Fair 2019-04-03 build site
html 905723c Benjmain Fair 2019-03-20 updated link
Rmd 8f7c737 Benjmain Fair 2019-03-20 updated link
Rmd 8dd795f Benjmain Fair 2019-03-20 First analysis on workflowr
html 8dd795f Benjmain Fair 2019-03-20 First analysis on workflowr
html 5b477a3 Benjmain Fair 2019-03-19 Build site.
Rmd b1207ee Benjmain Fair 2019-03-19 Start workflowr project.

Welcome to my research website.

QC

Association testing with various models

  • first iteration: description: lmm with KING-robust GRM thresholded at 0, and 3 genotype PCs
  • Check residuals after regressing out some covariates
  • second iteration: description: lm with 5 genotype PCs (PCs 4 and 5 takes into account some first hand relatedness) and more stringent genotype filtering. Also, outlier sample MD_And dropped from analysis
  • Third iteration
  • fourth iteration: description, lmm with 4 PCs and 3 Genotype PCs, used STAR RNA-seq CPM for less outliers. Fixed big bug that was permuting samples, resulting in no true hits in previous iterations. Here I used standardization and qqnorm.

Conservation and GO/GSEA analysis

  • GO analysis, FDR=0.1 overlap enrichment analysis of eGenes across humans and chumps, and gene ontology analysis of eGenes based on eGene classification defined at FDR=0.1 threshold. Also, a set of similar analyses using GSEA methodology, which is based on relative ranking of eGenes between species.
  • Conservation analysis, FDR=0.1 analysis of conservation of coding sequence (percent identity and dN/dS) based on eGene classification defined at FDR=0.1
  • Conservation analysis, HumanTop600_eGenes analysis of conservation of coding sequence (percent identity and dN/dS) based on eGene classification defined at FDR=0.1 for chimp and top600 qvalue genes for human.
  • Tissue sharing, both FDR=0.1 and Top600 analysis of number of GTEx tissues eGenes are detected in for shared and species specific eGenes. As before, I classify species specific and shared eGenes using either FDR=0.1 for both species, or using FDR-0.1 for chimp and top600 qvalue for human.
  • Conservation analysis, most high-variance genes analysis of conservation of coding sequence (percent identity and dN/dS) based on within species variance of expression. A useful comparison for the similar analysis above.
  • More thourough analyses looking at gene variance within and between species after adjusting for expression.

Power analysis for inter-species differential expression

  • PowerAnalysisFromOrinalDataset DE gene analysis based on subsampling ~39 chimp samples & 50 human samples (mostly GTEx)… Note that there are some outlier samples that I want to purge in later iterations of this analysis.

Differential contacts

  • Do differential DNA contacts between species explain differences in eGene character between species.
  • First crude analysis In this analysis I asked whether the there is a correlation between the rank difference in eGenes between species, and the difference in the sum of contacts in each species’ cis-window for each gene
  • There was a slight but significant correlation, but I worry about a potential bias introduced by the fact that eGene significance for humans was based on cis-eQTL calling with a 1MB window and chimp was a 250kB window. I should control for this.
  • Check that human lead snps in 250kB window are reasonable As expected, the p-value for lead snps within 250kb is well correlated for the eGene p-value, with the exception that there are many genes with much lower eGene pvalues probably because there is a better SNP >250kb away
  • After controlling for cis-window-size

Shared polymorphic loci

  • QQ Plot of species shared polymorphisms Of all the shared polymorphic loci (putative targets of balancing selection), do they have inflated cis-eQTL P-values compared to a random set of snp-gene tests.