Usual behavior: Attempts all steps in a task before moving on to the next task. This is especially useful if intermediate files are created and deleted over several steps within a task, and if those files would take up too much space if intermediate files from one step of all tasks were simultaneously present. This function also provides fault tolerance, retries, and using file existence as a first check on which tasks/steps are already built (faster than the remake practice of checking file hashes, which are only checked here after all files' presence suggest that everything is built).
Important: if you want the "usual behavior" from this function, delete any
task targets that are files and are known to be out of date before
starting. Out-of-date files will only be checked and rerun at the very end,
whereas missing files will be tried as many as num_tries
times.
1 2 3 4 5 6 7 8 9 10 11 12 |
task_plan |
task plan as created by |
task_makefile |
file name of the .yml makefile for these tasks |
task_names |
NULL to build all tasks, or character vector of specific tasks to build |
step_names |
NULL to build all final_steps from the task plan (see
|
num_tries |
integer number of times to retry looping through all remaining tasks |
sleep_on_error |
integer number of seconds to sleep immediately after a failed task. Especially useful if the error was likely to be inconsistent (e.g., a temporary network issue) and might not occur again if we wait a while |
ind_ext |
the indicator file extension passed to |
verbose |
define the format of task messages. Use TRUE for progress bar for the status of each task, and FALSE for no output |
force |
logical. If TRUE, targets specified by task_names (NULL for all
tasks) and step_names (NULL for the final step) will be deleted with |
n_cores |
integer How many cores should be utilized when executing the task plan? Defaults to one (no parallelization). |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.