rmarkdown
& knitr
capture everything
written to stdout
, which includes all output from document
chunks, including progress bars, such as those supplied
by dplyr
.
To enable progress reporting even when using rmarkdown
documents, the progress bar supplied here can write output to any
connection, including stdout
, stderr
, and any
opened file.
Load the package, and define the function that will use the progress bar. This particular example is courtesy of Bob Rudis.
There are two ways to choose the output:
make_kpb_output_decisions()
NULL
for no
output)make_kpb_output_decisions()
# not run
pb <- progress_estimated(length(letters))
purrr::map_int(letters, arduously_long_nchar, .pb = pb)
In the terminal, this should push results to stdout
, in
knitr
/ rmarkdown
it will get pushed to
stderr
.
If you want the progress to appear when in the terminal, but not when
running via the RStudio Knit
button or
Rscript
, then you can supply an option to suppress progress
output in non-interactive running:
If you want log-files displaying progress, you can use the following options:
This will push all progress to a log-file, by default to kpb_output.log.
Adding more options will provide finer control:
Now progress will be saved in my_logfile.log.
If you are using rmarkdown
and want to make log-files
based on the chunk labels, then you would use the
kpb.log_pattern
option:
This will generate a log-file for each rmarkdown
chunk,
and prepend each one with pb_out_.
Note: kpb.log_file
and
kpb.log_pattern
should not both be set in a single run, and
kpb.log_file
trumps kpb.log_pattern
.
In this case, you can simply pass a connection directly into
progress_estimated
:
# to terminal, or print in a knitr chunk
pb <- progress_estimated(length(letters), progress_location = stdout())
# to stderr, so visible from knitr
pb <- progress_estimated(length(letters), progress_location = stderr())
# to a file, visible using tailf
pb <- progress_estimated(length(letters), progress_location = file("progress.log", open = "w"))