Last updated: 2020-04-12

Checks: 2 0

Knit directory: misc/

This reproducible R Markdown analysis was created with workflowr (version 1.6.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! 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:    .Rhistory
    Ignored:    .Rproj.user/

Untracked files:
    Untracked:  analysis/contrainedclustering.Rmd
    Untracked:  analysis/deconvSimulation2.Rmd
    Untracked:  analysis/ideas.Rmd
    Untracked:  analysis/methylation.Rmd
    Untracked:  code/sccytokines.R
    Untracked:  code/scdeCalibration.R
    Untracked:  data/bart/
    Untracked:  data/cytokine/DE_controls_output_filter10.RData
    Untracked:  data/cytokine/DE_controls_output_filter10_addlimma.RData
    Untracked:  data/cytokine/README
    Untracked:  data/cytokine/test.RData
    Untracked:  data/cytokine_normalized.RData
    Untracked:  data/deconv/
    Untracked:  data/scde/

Unstaged changes:
    Modified:   analysis/CPM.Rmd
    Modified:   analysis/deconvSimulation.Rmd
    Modified:   analysis/deconvolution.Rmd
    Modified:   analysis/index.Rmd
    Modified:   analysis/limma.Rmd
    Deleted:    data/mout_high.RData
    Deleted:    data/scCDT.RData
    Deleted:    data/sva_sva_high.RData

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 b10c3c1 DongyueXie 2020-04-12 wflow_publish(“analysis/gsea.Rmd”)

Introduction

This is a summary of Irizarry et al 2009

Goal: Incorporating biological information into differential expression analysis.

The very common differential expression analysis is referred to as margianl approach: decide on a null hypothesis, test this hypothesis for each gene, produce a p-value, and attach a significance level that accounts for multiplicity.

In gesa, gene categories or gene sets are formed prior to the statistical analysis. It is more common to use category definitions from the Gene Ontology project.

Aggregate score approach: assign scores to each gene set based on all the gene-specific scores for that gene set.

For a gene set \(A_g\), each gene in it has a t-statistics \(t_i\), for \(i\in A_g\). We want to assign a gene set score \(E_g\) and a significant level that tells how \(t_i, i\in A_g\) differ from \(t_i,i\notin A_g\).

Some test proposed: K-S test, t-test, \(\chi^2\) test.

Can we do simultaneous RUV, and GESA? via regression and factor analysis.

Also think about regresing covariate on loadings.