Replies: 1 comment
-
|
The development version of future.batchtools implements a patch for a batchtools bug that has caused issues for some Slurm users when launching jobs (https://future.batchtools.futureverse.org/news/index.html). It should make it more stable. Install it as: remotes::install_github("futureverse/future.batchtools", ref="develop")Looking at your example, I think the built-in job-script template may handle it, using something like: library(future)
plan(future.batchtools::batchtools_slurm, resources = list(
modules = c("r/gcc/4.2.0"),
envs = c(DEBUGME = Sys.getenv("DEBUGME")),
time = "01:00:00", # walltime=60 => 60s
"cpus-per-task" = 1,
"mem-per-cpu" = "1024M"
ntasks = 1
))
f <- future(sessionInfo())
info <- value(f)
print(info)
If you really need this, please let me know. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello All,
I'm having an issue with future.batchtools that I've been unable to resolve: batchtools::submitJobs fails when called from future.batchtools, but not when called from batchtools. I believe it may be a problem with how future.batchtools handles the config file, but I'm not sure.
Running with batchtools works as expected. R loads my batchtools temp file and configuration file.
Running using future.batchtools fails to submit jobs.
batchtools.slurm.tmpl:
batchtools.conf.R
Note: The HPC login node is named "log-3"
Beta Was this translation helpful? Give feedback.
All reactions