A minimal, unifying API for scripts and packages to report progress updates from anywhere including when using parallel processing.  The package is designed such that the developer can to focus on what progress should be reported on without having to worry about how to present it.  The end user has full control of how, where, and when to render these progress updates, e.g. in the terminal using utils::txtProgressBar() or progress::progress_bar(), in a graphical user interface using utils::winProgressBar(), tcltk::tkProgressBar() or shiny::withProgress(), via the speakers using beep::beepr(), or on a file system via the size of a file. Anyone can add additional, customized, progression handlers. The 'progressr' package uses R's condition framework for signaling progress updated. Because of this, progress can be reported from almost anywhere in R, e.g. from classical for and while loops, from map-reduce API:s like the lapply() family of functions, 'purrr', 'plyr', and 'foreach'. It will also work with parallel processing via the 'future' framework, e.g. future.apply::future_lapply(), furrr::future_map(), and 'foreach' with 'doFuture'. The package is compatible with Shiny applications.

An Inclusive, Unifying API for Progress Updates

package-ubuntu-20.04-r-4.0.5#cran#progressr-0.10.0

<p>A Global Calling Handler For 'progression':s
</p>

<table summary="R argblock"><tr valign="top">
<td><code>progression</code></td>
<td>
<p>A <a href="progression.html">progression</a> conditions.</p>
</td>
</tr></table>

<p>This function requires R (&gt;= 4.0.0) - the version in which global calling
handlers where introduces.
</p>

package-ubuntu-20.04-r-4.0.5#cran#progressr-0.10.0#docs#global_progression_handler

global_progression_handler

Description

Usage

Arguments

Value

Requirements

progressr

We don't support your browser anymore