Process metadata files ‘SOFTWARE.bib’ and ‘DATA.bib’ to set up software and data files required for the analysis.
taf.boot(software = TRUE, data = TRUE, clean = TRUE, force = FALSE, taf = NULL, quiet = FALSE)
whether to process
whether to process
whether to remove existing
a convenience flag where
whether to suppress messages reporting progress.
clean = TRUE then:
clean.library are run if
‘SOFTWARE.bib’ is processed.
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
TRUE to download and install everything declared in
Logical vector indicating which metadata files were processed.
This function should be called from the top directory of a TAF analysis. It looks for a directory called ‘bootstrap’ and prepares data files and software according to metadata specifications.
The boot procedure consists of the following steps:
bootstrap/SOFTWARE.bib metadata file exists, it is
bootstrap/DATA.bib metadata file exists, it is processed.
After the boot procedure, software and data have been documented and are ready to be used in the subsequent analysis. Specifically, the procedure populates up to three new directories:
bootstrap/data with data files.
bootstrap/library with R packages compiled for the local
bootstrap/software with software files, such as R packages in
tar.gz source code format.
Model settings and configuration files can be set up within
see TAF Wiki.
draft.software can be used to
create initial draft versions of ‘DATA.bib’ and ‘SOFTWARE.bib’
taf.library loads a package from
TAF-package gives an overview of the package.
## Not run: taf.boot() ## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.