Parents (Total: 13)

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

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	C9C4AD97BB1176BC364409A7593C099B
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	lp153.1.12
PackageVersion	0.6.0
SHA-1	8ED2FB08222A66B38A755310F5B9E52F08158B08
SHA-256	A44BA3C4FA2C56725A7E588A1C209E341A4A5DBBA73527D1D04ADDC5D8AE2ECC

Key	Value
MD5	17C074BABD5AE9754A1E44F7844F7E4F
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	D72E4BA7FDB4627BA1DB142176511A1BD740B5EA
SHA-256	97A66F552C3AE4D87CCEC93A3B82E7B179C09E0D8A51D68E76BC76E93432BCBB

Key	Value
MD5	433A5295BE1898416B822EDB41682543
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	A2D87CCD782205BE38E9257EFD15C97D7C050F6E
SHA-256	337B4977ECD21CBEE6F1E92BB5EF9DEAB62A961468624D73FF3D8E16B04E836C

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	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

Key	Value
MD5	6C8FBEBEEA3FE2347A840D28EBF0D594
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	lp151.1.14
PackageVersion	0.6.0
SHA-1	FBD51DBA7205AC4E2636D9F6DCE1757725B572C0
SHA-256	A4D353E0B232351CFD77057848695C5549CBC59AD0CF5791B627152CD38BCD98

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
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	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	7D53F94CF49F9BC13028FC96F8A0D2BE
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.27
PackageVersion	0.6.0
SHA-1	BF6894A8A08D6B9E467830C0FA8FFC0EDF525AAD
SHA-256	5830BC8239B3A22F5963352535AD7360BF49C302B37F94DE73679C5E7FB13A8F

Key	Value
MD5	EDB018578A10FCD264A64F886C435236
PackageArch	armv7hl
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.22
PackageVersion	0.6.0
SHA-1	A1158B73DA56CDAB9CD0A8F1B5140F1F4A37F508
SHA-256	155B74454C04A1C75AE445A674273434A247FB0BF15CA758B743481FD5BE1F84

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