403Webshell
Server IP : 82.208.35.60  /  Your IP : 216.73.216.238
Web Server : Apache/2.4.55 (FreeBSD) OpenSSL/1.1.1q-freebsd PHP/7.3.31
System : FreeBSD server7.d2m.cz 12.4-RELEASE-p9 FreeBSD 12.4-RELEASE-p9 GENERIC amd64
User : studiokobylisy_cz ( 1008)
PHP Version : 7.3.31
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /usr/ports/devel/R-cran-progressr/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/ports/devel/R-cran-progressr/pkg-descr
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 APIs 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.

Youez - 2016 - github.com/yon3zu
LinuXploit