Last updated: 2019-04-09

Checks: 2 0

Knit directory: dsc-linreg/analysis/

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

R Markdown file: up-to-date

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.

Repository version: f8959f4

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:    .sos/
    Ignored:    analysis/.sos/
    Ignored:    dsc/.sos/
    Ignored:    dsc/linreg/

Unstaged changes:
    Modified:   analysis/results_overview.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 f8959f4 Peter Carbonetto 2019-04-09 wflow_publish(c(“index.Rmd”, “usage_instructions.Rmd”))
html e54452c Peter Carbonetto 2019-04-09 Made a few small revisions to the usage instructions.
Rmd 070f004 Peter Carbonetto 2019-04-09 wflow_publish(“usage_instructions.Rmd”)
Rmd d4d0415 Peter Carbonetto 2019-04-09 Re-organized some files, and moved usage instructions to workflowr page.

Please follow these steps to start using the linear regression DSC.

First, install DSC.

Next, install R, as well as the R packages used. The devtools and glmnet packages can be installed from CRAN:

install.packages("devtools")
install.packages("glmnet")
install.packages("ggplot2")
install.packages("cowplot")

The susieR, varbvs and dscrutils packages can be installed from GitHub using devtools:

library(devtools)
install_github("stephenslab/susieR")
install_github("pcarbo/varbvs",subdir = "varbvs-R")
install_github("stephenslab/dsc",subdir = "dscrutils")

Clone or download this git repository.

Now you should have everything you need to run the DSC. Navigate to the “dsc” directory inside your local copy of the git repository, and run it with this command (here we have chosen 4 threads, but you may want to adjust the number of threads to better suit your computer):

dsc -c 4 linreg.dsc

Go grab a coffee while you wait for the DSC to run. It may take some time, perhaps as long as 30 minutes, for all the DSC pipelines to complete.

Once the DSC has finished running, you may want to work through this short analysis to explore the results of the DSC in R or RStudio. When running the R code, make sure your working directory is set to the “analysis” directory in the git repository.

DSC is specifically designed to be extended—please make improvements to this DSC by modifying our experiments, or by adding new methods, data scenarios or evaluation metrics.