.purge

A checksums file, e.g., created by Checksums(..., write = TRUE)

checkSums

Logical or Integer. <code>0/FALSE</code> (default) keeps existing
<code>CHECKSUMS.txt</code> file and
<code>prepInputs</code> will write or append to it. <code>1/TRUE</code> will deleted the entire
<code>CHECKSUMS.txt</code> file. Other options, see details.

purge

Character string giving the path to the eventual file
(raster, shapefile, csv, etc.) after downloading and extracting from a zip
or tar archive. This is the file before it is passed to
<code>postProcess</code>. Currently, the internal checksumming does not checksum
the file after it is <code>postProcess</code>ed (e.g., cropped/reprojected/masked).
Using <code>Cache</code> around <code>prepInputs</code> will do a sufficient job in these cases.
See table in <code><a rd-options="" href="/link/preProcess?package=reproducible&version=1.1.1" data-mini-rdoc="reproducible::preProcess">preProcess</a></code>.

targetFile

Optional character string giving the path of an archive
containing <code>targetFile</code>, or a vector giving a set of nested archives
(e.g., <code>c("xxx.tar", "inner.zip", "inner.rar")</code>). If there is/are (an) inner
archive(s), but they are unknown, the function will try all until it finds
the <code>targetFile</code>. See table in <code><a rd-options="" href="/link/preProcess?package=reproducible&version=1.1.1" data-mini-rdoc="reproducible::preProcess">preProcess</a></code>.

internal

Collection of high-level, robust, machine- and OS-independent tools
for making deeply reproducible and reusable content in R.
The three workhorse functions are Cache, prepInputs, and Require;
these allow for nested caching, robust to environments, and objects with
environments (like functions), and data retrieval and processing, and
package handling in continuous workflow environments. In all cases,
efforts are made to make the first and subsequent calls of functions have
the same result, but vastly faster at subsequent times by way of checksums
and digesting. Several features are still under active development, including
cloud storage of cached objects, allowing for sharing between users.

Eliot J B

reproducible

A Set of Tools that Enhance Reproducibility Beyond Package
Management

Eliot J B McIntire

Alex M Chubaty

Tati Micheletti

Ceres Barros

Ian Eddy

Her Majesty the Queen in Right of Canada, as represented by the Minister of Natural Resources Canada 

.purge function

Character string giving the path to the eventual file
(raster, shapefile, csv, etc.) after downloading and extracting from a zip
or tar archive. This is the file before it is passed to
<code>postProcess</code>. Currently, the internal checksumming does not checksum
the file after it is <code>postProcess</code>ed (e.g., cropped/reprojected/masked).
Using <code>Cache</code> around <code>prepInputs</code> will do a sufficient job in these cases.
See table in <code><a rd-options='' href='preProcess'>preProcess</a></code>.

Optional character string giving the path of an archive
containing <code>targetFile</code>, or a vector giving a set of nested archives
(e.g., <code>c("xxx.tar", "inner.zip", "inner.rar")</code>). If there is/are (an) inner
archive(s), but they are unknown, the function will try all until it finds
the <code>targetFile</code>. See table in <code><a rd-options='' href='preProcess'>preProcess</a></code>.

Optional character string indicating the URL to download from.
If not specified, then no download will be attempted. If not entry
exists in the <code>CHECKSUMS.txt</code> (in <code>destinationPath</code>), an entry
will be created or appended to. This <code>CHECKSUMS.txt</code> entry will be used
in subsequent calls to
<code>prepInputs</code> or <code>preProcess</code>, comparing the file on hand with the ad hoc
<code>CHECKSUMS.txt</code>. See table in <code><a rd-options='' href='preProcess'>preProcess</a></code>.

.purge: Purge individual line items from checksums file

Description

Usage

Arguments