Description Usage Arguments Details Value See Also Examples
A data processing workflow might include multiple processing steps, with
each step being performed by a separate R script. These multiple steps are linked by
the files that one step writes and the next step in the workflow reads. The traceRuns
method finds these connections between executions to determine the executions that
comprise a processing workflow, and returns information for each run in the processing workflow
including all files that were read and written by each script.
1 2 3 4 5 6 7 8 | traceRuns(recordr, ...)
## S4 method for signature 'Recordr'
traceRuns(recordr, id = as.character(NA),
file = as.character(NA), start = as.character(NA),
end = as.character(NA), tag = as.character(NA),
error = as.character(NA), seq = as.character(NA),
orderBy = "-startTime", direction = "both", quiet = TRUE, ...)
|
recordr |
a Recordr instance |
... |
additional parameters |
id |
The identifier for a run. Either |
file |
The name of script to match |
start |
Match runs that started in this time range (inclusive) Times must be entered in the form 'YYYY-MM-DD HH:MM:SS' but can be shortened to not less that "YYYY" |
end |
Match runs that ended in this time range (inclusive) Times must be entered in the form 'YYYY-MM-DD HH:MM:SS' but can be shortened to not less that "YYYY" |
tag |
The text of tag to match |
error |
The text of error message to match. |
seq |
The sequence number for a run. #' @param id The execution identifier of a run to view |
orderBy |
Sort the results according to the specified column. A hypen ('-') prepended to the column name denoes a descending sort. The default value is "-startTime" |
direction |
The direction to trace the lineage, either |
quiet |
A |
If the run id
or seq
number is know for the run to be traced, then one or the
other of these values can be used. Alternatively, other run attributes can be used to determine the run to be traced,
such as file
, start
, etc. If these other search parameters are used and multiple runs are selected,
only the first run selected will be traced. These search parameters can be used together to easily find certain runs,
for example, the latest run of a particular script, the latest run with a specified tag specified, etc. (see examples).
A list of the execution identifiers that are in the processing workflow.
Recordr
class description
1 2 3 4 5 6 7 8 9 | ## Not run:
# Trace lineage for the run with sequence number '101'
linkedRuns <- traceRuns(recordr, seq=101)
# Trace lineage for the last execution of script "runModel.R"
linkedRuns <- traceRuns(recordr, file="runModel.R", orderBy="-startTime")
# Trace lineage for the last execution with the tag 'best run yet!' specified.
linkedRuns <- traceRuns(recordr, tag="best run yet!", orderBy="-startTime")
## End(Not run)
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.