Triggers of a target.
drake_triggers( command = TRUE, depend = TRUE, file = TRUE, seed = TRUE, format = TRUE, condition = FALSE, change = NULL, mode = c("whitelist", "blacklist", "condition") )
Logical, whether to rebuild the target if the
Logical, whether to rebuild if a non-file dependency changes.
Logical, whether to rebuild the target if a
knitr_in()file changes. Also applies to external data tracked with
target(format = "file").
Logical, whether to rebuild the target if the seed changes. Only makes a difference if you set a custom
seedcolumn in your
drake_plan()at some point in your workflow.
Logical, whether to rebuild the target if the choice of specialized data format changes: for example, if you use
target(format = "qs")one instance and
target(format = "fst")the next. See https://books.ropensci.org/drake/plans.html#special-data-formats-for-targets # nolint for details on formats.
R code (expression or language object) that returns a logical. The target will rebuild if the code evaluates to
R code (expression or language object) that returns any value. The target will rebuild if that value is different from last time or not already cached.
A character scalar equal to
"condition". With the
modeargument, you can choose how the
conditiontrigger factors into the decision to build or skip the target. Here are the options.
"whitelist"(default): we rebuild the target whenever
TRUE. Otherwise, we defer to the other triggers. This behavior is the same as the decision rule described in the "Details" section of this help file.
"blacklist": we skip the target whenever
FALSE. Otherwise, we defer to the other triggers.
"condition": here, the
conditiontrigger is the only decider, and we ignore all the other triggers. We rebuild target whenever
TRUEand skip it whenever