progressr (Q60929): Difference between revisions

From MaRDI portal
Importer (talk | contribs)
Changed an Item
Added link to MaRDI item.
 
links / mardi / namelinks / mardi / name
 

Latest revision as of 19:55, 12 March 2024

An Inclusive, Unifying API for Progress Updates
Language Label Description Also known as
English
progressr
An Inclusive, Unifying API for Progress Updates

    Statements

    0.13.0
    10 January 2023
    0 references
    0.4.0
    23 January 2020
    0 references
    0.5.0
    17 April 2020
    0 references
    0.6.0
    19 May 2020
    0 references
    0.7.0
    11 December 2020
    0 references
    0.8.0
    10 June 2021
    0 references
    0.9.0
    24 September 2021
    0 references
    0.10.0
    19 December 2021
    0 references
    0.10.1
    3 June 2022
    0 references
    0.11.0
    2 September 2022
    0 references
    0.12.0
    13 December 2022
    0 references
    0.14.0
    10 August 2023
    0 references
    0 references
    0 references
    0 references
    10 August 2023
    0 references
    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(), cli::cli_progress_bar(), in a graphical user interface using utils::winProgressBar(), tcltk::tkProgressBar() or shiny::withProgress(), via the speakers using beepr::beep(), 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.
    0 references
    0 references
    0 references
    0 references