build_drake_graph
Use drake_config()
instead.
build_drake_graph(plan, targets = plan$target, envir = parent.frame(),
verbose = 1L, jobs = 1, console_log_file = NULL,
trigger = drake::trigger(), cache = NULL)
Workflow plan data frame.
A workflow plan data frame is a data frame
with a target
column and a command
column.
(See the details in the drake_plan()
help file
for descriptions of the optional columns.)
Targets are the objects that drake generates,
and commands are the pieces of R code that produce them.
You can create and track custom files along the way
(see file_in()
, file_out()
, and knitr_in()
).
Use the function drake_plan()
to generate workflow plan
data frames.
Character vector, names of targets to build.
Dependencies are built too. Together, the plan
and
targets
comprise the workflow network
(i.e. the graph
argument).
Changing either will change the network.
Environment to use. Defaults to the current
workspace, so you should not need to worry about this
most of the time. A deep copy of envir
is made,
so you don't need to worry about your workspace being modified
by make
. The deep copy inherits from the global environment.
Wherever necessary, objects and functions are imported
from envir
and the global environment and
then reproducibly tracked as dependencies.
Integer, control printing to the console/terminal.
0
: print nothing.
1
: print targets, retries, and failures.
2
: also show a spinner when preprocessing tasks are underway.
Maximum number of parallel workers for processing the targets.
You can experiment with predict_runtime()
to help decide on an appropriate number of jobs.
For details, visit
https://ropenscilabs.github.io/drake-manual/time.html.
Optional character scalar of a file name or
connection object (such as stdout()
) to dump maximally verbose
log information for make()
and other functions (all functions that
accept a config
argument, plus drake_config()
).
If you choose to use a text file as the console log,
it will persist over multiple function calls
until you delete it manually.
Fields in each row the log file, from left to right:
- The node name (short host name) of the
computer (from Sys.info()["nodename"]
).
- The process ID (from Sys.getpid()
).
- A timestamp with the date and time (in microseconds).
- A brief description of what drake
was doing. The fields are separated by pipe symbols (
"|"`).
Name of the trigger to apply to all targets.
Ignored if plan
has a trigger
column.
See trigger()
for details.
drake cache as created by new_cache()
.
See also drake_cache()
.
An igraph
object.
Deprecated on 2018-11-02.