TAF (version 4.3.1)

taf.boot: Boot TAF Analysis

Description

Process metadata files SOFTWARE.bib and DATA.bib to set up software and data files required for the analysis.

Usage

taf.boot(software = TRUE, data = TRUE, clean = TRUE, force = FALSE,
  taf = NULL, quiet = FALSE, ...)

Value

Logical vector indicating which metadata files were processed.

Arguments

software

whether to process SOFTWARE.bib.

data

whether to process DATA.bib.

clean

whether to clean directories during the boot procedure.

force

whether to remove existing boot/data, boot/library, and boot/software directories before the boot procedure.

taf

a convenience flag where taf = TRUE sets software, data, clean, and force to TRUE, as is done on the TAF server. Any other value of taf is ignored.

quiet

whether to suppress messages reporting progress.

...

passed to process.entry.

Details

If clean = TRUE then:

1. clean.software and clean.library are run if SOFTWARE.bib is processed.

2. clean.data is run if DATA.bib is processed.

The default behavior of taf.boot is to skip downloading of remote files (GitHub resources, URLs, boot scripts) and also skip installing R packages from GitHub if the files seem to be already in place. This is done to speed up the boot procedure as much as possible. To override this and guarantee that all data and software files are updated, pass force = TRUE to download and install everything declared in SOFTWARE.bib and DATA.bib.

See Also

draft.data and draft.software can be used to create initial draft versions of DATA.bib and SOFTWARE.bib metadata files.

taf.library loads a package from boot/library.

TAF-package gives an overview of the package.

Examples

if (FALSE) {
taf.boot()
}