Parents (Total: 18)

The searched file hash is included in 18 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	FCAD640A2759F9B6EB42E5FB9189CF52
PackageArch	i586
PackageDescription	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.
PackageName	R-progressr
PackageRelease	1.27
PackageVersion	0.6.0
SHA-1	0005B925FFF82B126F38E6F98CAD3EEFE1975561
SHA-256	BB88235F254ED974367268A7D95945CDA7AB9A189EA7B0E3E74F2AA0485C47C5

Key	Value
MD5	D7D78214C41C0FD419D7F94E16F7DCA7
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	1.14
PackageVersion	0.6.0
SHA-1	0EB38F53AEDB4F52B998721BD50DE085F79C1A5C
SHA-256	8440DC1B1CCA6E28A06E06B6CA6708A482DA15B1BCA585E63AF330B1526839FD

Key	Value
MD5	544F381C6E75AEC7DFFD7505D2844299
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	1.1
PackageVersion	0.10.0
SHA-1	2D21D3D9BCABE7370659F8206090B773A8424A48
SHA-256	BA530A8DF27D0CC587AEB923438BC08C796D7808720D4B5517D6342D50152533

Key	Value
MD5	5EFE19763105365C15905D74449A3A9E
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	lp150.1.12
PackageVersion	0.6.0
SHA-1	3B874E3716C01982CB0AC2079FFCCEBE560693BC
SHA-256	DB489D6186E0B6569993E48F6868607592DB08B1073E33CDC755744FCA8EB97F

Key	Value
FileSize	258224
MD5	DCC575A9C86151D6C435C3B53633C3E7
PackageDescription	GNU R inclusive, unifying API for progress updates 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.
PackageMaintainer	Debian R Packages Maintainers <r-pkg-team@alioth-lists.debian.net>
PackageName	r-cran-progressr
PackageSection	gnu-r
PackageVersion	0.9.0-1
SHA-1	3C83DCE31548E6D88DA2CC448DB29282F4A8BDF1
SHA-256	196999C36D1D850D0707030680E1DC86741E477404C5D07294EDBB65E27A954E

Key	Value
MD5	98279AB1BD6BDFA6CA811A185A4DF5E7
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	1.6
PackageVersion	0.6.0
SHA-1	3CF8B3CB7F3FAF030E8BBC1C278A211831B5C251
SHA-256	8BB668C748C7CE9B1BF5893B199323202DFBB4CCDDD658F60E1FEE023BF182BE

Key	Value
MD5	244A1653888610850795A0FBEDB4DAC7
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	1.28
PackageVersion	0.6.0
SHA-1	3EF543731AE3622157921D822F94A31478A1A502
SHA-256	D85DD1CC8A79CD3FE2D776DD7B23FD52C5ABEC47A8C3F60301500DB86797B763

Key	Value
MD5	51E289678ED1D086D26DA4E1842ABC0F
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	lp154.1.1
PackageVersion	0.10.0
SHA-1	633518379A14C603731BCFD0119550BFECA7430B
SHA-256	30582021379EF40B7240DFB9188B30B5F20DEDAE67E02CE23805DA66E7EACAFF

Key	Value
MD5	BB757C3233702052363A133B93AC9DBF
PackageArch	x86_64
PackageDescription	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.
PackageName	R-progressr
PackageRelease	lp152.1.7
PackageVersion	0.6.0
SHA-1	673C70103C2B14808EC351761F6E8DE26B9F0369
SHA-256	C288552A16C3286C5C742D944784614685F94235FC2903C3D5B441F5E36FE62F

Key	Value
MD5	43481340B1313B49F6746EDB309CDD67
PackageArch	i586
PackageDescription	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.
PackageName	R-progressr
PackageRelease	1.28
PackageVersion	0.6.0
SHA-1	7F06FCA9FC65B48EE172C294FA77C8899AF473F6
SHA-256	FDE305180B8DFC3B2883ADF5A40676BFD42055405281AB2AE17C0E2AD677264D