Last updated: 2019-05-06

Checks: 2 0

Knit directory: W_shredder/

This reproducible R Markdown analysis was created with workflowr (version 1.3.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:    .DS_Store
    Ignored:    .Rhistory
    Ignored:    .Rproj.user/
    Ignored:    Proc_B_manuscript/.DS_Store
    Ignored:    data/sim_results/
    Ignored:    docs/figure/

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 52387cb lukeholman 2019-05-06 wflow_publish(files = "*")
Rmd f84ee9f Luke Holman 2018-08-11 First commit
html f84ee9f Luke Holman 2018-08-11 First commit
html 54a8a35 Luke Holman 2018-07-16 Build site.
Rmd 6f3f950 Luke Holman 2018-07-16 Start workflowr project.

Defining functions used to run the simulation

Click here to see all functions used in the model.

Running the simulation using the SLURM workload manager

Click here to see how the model was run.

Analysing and plotting the results of the simulation

Click here to see how the model was run.