Last updated: 2019-10-02
Checks: 2 0
Knit directory: for-future-reference/
This reproducible R Markdown analysis was created with workflowr (version 1.4.0.9001). 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: .binder/
Untracked: docs/figure/summation.Rmd/example-1.pdf
Untracked: docs/figure/summation.Rmd/example-1.svg
Untracked: docs/figure/variance.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 | 5602422 | John Blischak | 2019-10-02 | Document how to pin a pkg in a conda env |
conda is a package and environment manager.
Package, dependency and environment management for any language—Python, R, Ruby, Lua, Scala, Java, JavaScript, C/ C++, FORTRAN, and more.
conda config --add pinned_packages conda-forge::r-callr=3.3.0To only pin the package in the current environment, use the --env flag:
–env Write to the active conda environment .condarc file. If no environment is active, write to the user config file.
conda config --env --add pinned_packages conda-forge::r-callr=3.3.0Note that this isn’t well-documented. The current conda docs recommend pinning a package by manually creatingthe file pinned in the conda-meta subdirectory of the environment, and then adding the pins there.