Last updated: 2020-04-28

Checks: 2 0

Knit directory: mr_mash_test/

This reproducible R Markdown analysis was created with workflowr (version 1.6.1). 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: 247e5c3

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 247e5c3. 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:    .sos/
    Ignored:    code/fit_mr_mash.66662433.err
    Ignored:    code/fit_mr_mash.66662433.out
    Ignored:    dsc/.sos/
    Ignored:    dsc/outfiles/
    Ignored:    output/dsc.html
    Ignored:    output/dsc/
    Ignored:    output/dsc_OLD.html
    Ignored:    output/dsc_OLD/

Untracked files:
    Untracked:  code/plot_test.R
    Untracked:  dsc/dsc.scripts.html

Unstaged changes:
    Modified:   dsc/midway2.yml

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/license.Rmd) and HTML (docs/license.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 f2fa981 fmorgante 2020-04-28 Build site.
html e2c9550 fmorgante 2020-04-16 Build site.
html 161eea7 fmorgante 2020-04-16 Build site.
html dd40784 fmorgante 2020-04-16 Build site.
html 8f4456e fmorgante 2020-04-16 Build site.
html 422658e fmorgante 2020-04-16 Build site.
html 04f5485 fmorgante 2020-03-30 Build site.
html cc50c05 fmorgante 2020-03-30 Build site.
html 378e278 fmorgante 2020-03-30 Build site.
html 40cd0cf fmorgante 2020-03-30 Build site.
html b48d34d fmorgante 2020-03-30 Build site.
html 7a2afe7 fmorgante 2020-03-30 Build site.
html f7e2f68 fmorgante 2020-03-30 Build site.
html 4f5c291 fmorgante 2020-03-30 Build site.
html 8621d7d fmorgante 2020-03-30 Build site.
html d5773c9 fmorgante 2020-03-30 Build site.
html 07a9b4d fmorgante 2020-03-30 Build site.
html f2c716e fmorgante 2020-03-30 Build site.
html 8e7a5b5 fmorgante 2020-03-30 Build site.
html 4e9aad6 fmorgante 2020-03-30 Build site.
html 7911e81 fmorgante 2020-03-30 Build site.
html e1707b2 fmorgante 2020-03-30 Build site.
html b186ce3 fmorgante 2020-03-29 Build site.
Rmd 2c2c431 fmorgante 2020-03-28 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.