Future backends based on the 'batchtools' framework
Source:R/BatchtoolsFutureBackend-class.R
, R/batchtools_local.R
BatchtoolsFutureBackend.Rd
Future backends based on the 'batchtools' framework
Future backends based on the 'batchtools' framework
Arguments
- workers
(optional) The maximum number of workers the batchtools backend may use at any time. Interactive and "local" backends can only process one future at the time (
workers = 1L
), whereas HPC backends, where futures are resolved via separate jobs on a scheduler, can have multiple workers. In the latter, the default isworkers = NULL
, which will resolve togetOption("future.batchtools.workers")
. If neither are specified, then the default is100
.- resources
(optional) A named list passed to the batchtools template (available as variable
resources
). See Section 'Resources' inbatchtools::submitJobs()
more details.- conf.file
(optional) A batchtools configuration file.
- cluster.functions
(optional) A batchtools ClusterFunctions object.
- registry
(optional) A named list of settings to control the setup of the batchtools registry.
- finalize
If TRUE, any underlying registries are deleted when this object is garbage collected, otherwise not.
- ...
Additional arguments passed to
FutureBackend()
.