Implementations of lapply(), sapply(), tapply(), vapply() and friends that can be resolved using any future-supported backend, e.g. parallel on the local machine or distributed on a compute cluster. These future_*apply() functions come with the same pros and cons as the corresponding base-R *apply() functions but with the additional feature of being able to be processed via the future framework.
Version: | 0.2.0 |
Depends: | R (≥ 3.2.0), future (≥ 1.8.0) |
Imports: | globals (≥ 0.11.0) |
Suggests: | stats, listenv (≥ 0.7.0), R.rsp, markdown |
Published: | 2018-05-01 |
Author: | Henrik Bengtsson [aut, cre, cph], R Core Team [cph, ctb] |
Maintainer: | Henrik Bengtsson <henrikb at braju.com> |
BugReports: | https://github.com/HenrikBengtsson/future.apply/issues |
License: | LGPL-2.1 | LGPL-3 [expanded from: LGPL (≥ 2.1)] |
URL: | https://github.com/HenrikBengtsson/future.apply |
NeedsCompilation: | no |
Materials: | NEWS |
CRAN checks: | future.apply results |
Reference manual: | future.apply.pdf |
Vignettes: |
A Future for R: Apply Function to Elements in Parallel |
Package source: | future.apply_0.2.0.tar.gz |
Windows binaries: | r-devel: future.apply_0.2.0.zip, r-release: future.apply_0.2.0.zip, r-oldrel: future.apply_0.2.0.zip |
OS X binaries: | r-release: future.apply_0.2.0.tgz, r-oldrel: future.apply_0.1.0.tgz |
Old sources: | future.apply archive |
Reverse imports: | drake, kernelboot, origami, R.filesets, sperrorest |
Reverse suggests: | future.batchtools, future.callr |
Please use the canonical form https://CRAN.R-project.org/package=future.apply to link to this page.