Last updated: 2019-11-14

Checks: 2 0

Knit directory: BloomSail/

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.

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: 252f84d

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/
    Ignored:    data/TinaV/
    Ignored:    data/_merged_data_files/
    Ignored:    data/_summarized_data_files/

Untracked files:
    Untracked:  docs/reports/

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
html d61a468 jens-daniel-mueller 2019-11-14 Build site.
html f3277a5 jens-daniel-mueller 2019-11-08 Build site.
html 4256bcf jens-daniel-mueller 2019-11-08 Build site.
html 72687ee jens-daniel-mueller 2019-11-08 Build site.
html 74212a6 jens-daniel-mueller 2019-11-08 Build site.
html 33e3659 jens-daniel-mueller 2019-10-22 Build site.
html 1595fe9 jens-daniel-mueller 2019-10-21 Build site.
html a059c41 jens-daniel-mueller 2019-10-21 Build site.
html 32ec4f7 jens-daniel-mueller 2019-10-21 Build site.
html bafa88f jens-daniel-mueller 2019-10-21 Build site.
html 076a36b jens-daniel-mueller 2019-10-21 Build site.
html b2d0164 jens-daniel-mueller 2019-10-21 Build site.
html f2becd1 jens-daniel-mueller 2019-10-21 Build site.
html f91f17d jens-daniel-mueller 2019-10-21 Build site.
html fd500ed jens-daniel-mueller 2019-10-21 Build site.
html 9c7a03e jens-daniel-mueller 2019-10-21 Build site.
Rmd 31a2608 jens-daniel-mueller 2019-10-21 Start workflowr project.

What license are you using for your code? See choosealicense.com for help deciding. It’s a convention to save a file LICENSE in the root of your Git repo that contains the license text.

What license are you using for the written content on your site? It is traditional to choose a Creative Commons license for this type of content.

How should others cite your work? It’s a convention to save a file CITATION in the root of your Git repo that contains the citation information.