Closed coatless closed 4 years ago
Oh my. Thanks for spotting this and reporting here.
This looks like a cut'n'paste that originates from future.BatchJobs. I've updated the vignette + the README in the develop branch (=next release):
https://github.com/HenrikBengtsson/future.batchtools/tree/develop
@HenrikBengtsson thanks for the quick patch!
Two quick follow-up questions, following the batchtools
template:
resources
parameter as the ...
aren't picked up? Or, is it possible to set a configuration within conf
in BatchtoolsFuture()
?log.file
, job.name
, et cetera? Correct, resources
is how you pass options to the batchtools template. This is by design of the batchtools package, and specifically batchtools::submitJobs()
.
Those are also by design of the batchtools package.
I'm trying to do a nested future topology with torque cluster. However, when I run the code I'm getting the error of:
I've modified the example here:
https://cran.r-project.org/web/packages/future/vignettes/future-3-topologies.html
With information given in the
future.batchtools
vignette:https://cran.r-project.org/web/packages/future.batchtools/vignettes/future.batchtools.html
In particular, I'm using:
I've used the template
~/.batchtools.torque.tmpl
:Within the last line, I don't think that
rscript
variable is being set. Isfuture
generating an R script with the topology and then executing? This is also different from the.pbs
template configuration shipping withbatchtools
:https://github.com/mllg/batchtools/blob/fc896b349e86456506387b1a5cabba7e09f1a09f/inst/templates/torque-lido.tmpl#L76-L77