Last updated: 2022-03-09

Checks: 6 1

Knit directory: diff_driver_analysis/

This reproducible R Markdown analysis was created with workflowr (version 1.6.2). 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 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(20181210) 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 4099952. 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:    .Rproj.user/

Unstaged changes:
    Modified:   analysis/Introduction.Rmd
    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 repository in which changes were made to the R Markdown (analysis/Introduction.Rmd) and HTML (docs/Introduction.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
html 9409517 simingz 2021-09-13 add R package notes
html ea436cf simingz 2021-09-09 introduction
Rmd cbdb287 simingz 2021-09-06 model

Introduction

During adaptation, the strength of selection on a gene may vary in different individuals (cancer setting) or species (comparative genomic setting), two scenarios:

  • Different environments: select for different genes/pathways.
  • Same environment: but many possible ways of adapting to it, and each individual may evolve a different strategy.

For example: species adaptation to cold environment. Both scenarios are possible: (1) In some environment, more fatty foods, and selection of more fat to adapt; in other environments, selection of more hair and furs. (2) Same environmental pressure, but selection on either hair/furs or fat. In either case, species may have different hair and fat.

Our goal is to identify genes that drive adaption given the environment or genes that adapting to environment through a certain phenotype. We consider one gene a time and test if it drives adaptation under certain environment or via the given the phenotype. Let \(S_i\) be the sequence (mutation) of individual/species \(i\), \(w_i\) be the selection coefficient on the gene in \(i\). \(E_i\) be the environment for \(i\). Our model is \(E_i \rightarrow w_i \rightarrow S_i\). When studying a certain phenotype of the individual \(P_i\), we treat the phenotype as a marker of selection and our model is \(P_i \rightarrow w_i \rightarrow S_i\). In both cases,\(P(S_i| w_i)\), and \(w_i = f(P_i)\) or \(w_i = f(E_i)\), where we can use \(dN/dS\) to model how the sequence/mutation depends on selection. For simplicity, use \(E_i\) to represent individual level selection (either environment of phenotype).


sessionInfo()
R version 4.1.0 (2021-05-18)
Platform: x86_64-apple-darwin17.0 (64-bit)
Running under: macOS Mojave 10.14.6

Matrix products: default
BLAS:   /Library/Frameworks/R.framework/Versions/4.1/Resources/lib/libRblas.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/4.1/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     

loaded via a namespace (and not attached):
 [1] Rcpp_1.0.7        whisker_0.4       knitr_1.33        magrittr_2.0.1   
 [5] workflowr_1.6.2   R6_2.5.0          rlang_0.4.11      fansi_0.5.0      
 [9] stringr_1.4.0     tools_4.1.0       xfun_0.24         utf8_1.2.2       
[13] git2r_0.28.0      htmltools_0.5.1.1 ellipsis_0.3.2    rprojroot_2.0.2  
[17] yaml_2.2.1        digest_0.6.27     tibble_3.1.6      lifecycle_1.0.1  
[21] crayon_1.4.2      later_1.2.0       vctrs_0.3.8       promises_1.2.0.1 
[25] fs_1.5.0          glue_1.4.2        evaluate_0.14     rmarkdown_2.9    
[29] stringi_1.7.3     compiler_4.1.0    pillar_1.6.4      httpuv_1.6.1     
[33] pkgconfig_2.0.3