A Future API for Parallel and Distributed Processing using 'batchtools'
A batchtools bash backend that resolves futures sequentially via a Bas...
A batchtools backend that resolves futures sequentially in the current...
A batchtools backend that resolves futures sequentially in transient b...
A batchtools LSF backend resolves futures in parallel via a Load Shari...
A batchtools backend that resolves futures in parallel via forked back...
A batchtools openlava backend resolves futures in parallel via a OpenL...
A batchtools SGE backend resolves futures in parallel via a Sun/Son of...
A batchtools slurm backend resolves futures in parallel via a Slurm jo...
A batchtools backend that resolves futures in parallel via background ...
A batchtools TORQUE backend resolves futures in parallel via a TORQUE/...
A batchtools future is a future whose value will be resolved via batch...
FutureError class for errors related to BatchtoolsFuture:s
batchtools multicore futures
Batchtools futures for LSF, OpenLava, SGE, Slurm, TORQUE etc.
Removes a batchtools future
future.batchtools: A Future for batchtools
Temporarily tweaks the resources for the current batchtools strategy
Logged output of batchtools future
ClusterFunctions for Slurm Systems (patched)
Gets the number of batchtools workers
Prints a batchtools future
Options used for batchtools futures
Implementation of the Future API <doi:10.32614/RJ-2021-048> on top of the 'batchtools' package. This allows you to process futures, as defined by the 'future' package, in parallel out of the box, not only on your local machine or ad-hoc cluster of machines, but also via high-performance compute ('HPC') job schedulers such as 'LSF', 'OpenLava', 'Slurm', 'SGE', and 'TORQUE' / 'PBS', e.g. 'y <- future.apply::future_lapply(files, FUN = process)'.
Useful links