passing submitJobs parameters from BatchJobsParam
1
1
Entering edit mode
Alejandro Reyes ★ 1.9k
@alejandro-reyes-5124
Last seen 11 weeks ago
Novartis Institutes for BioMedical Rese…

Hi, 

I was using BiocParallel with BatchJobsParam and kept getting an error described here ( https://github.com/tudo-r/BatchJobs/issues/58 ). To avoid that error, I needed to pass the parameter job.delay from the function submitJobs (defined in BatchJobs), but I could not find a way pass this parameter to submitJobs when creating my BatchJobsParam object. By looking at the code, the only parameter that is passed to submitJobs from BatchJobsParam is 'resources':

submit.pars <- Filter(not_null, list(resources=resources))

So, what I end up doing was to manually modify my BatchJobsParam object:
 

cf <- makeClusterFunctionsLSF("/home/reyes/lsf.tmpl")
bjp <- BatchJobsParam( nCores,
    conffile="/g/huber/users/reyes/CLL/org/BatchJobs_config.R",
    cluster.functions=cf,resources = list("queue" = "medium_priority", "memory"="8000", "cpus"="1" ))

bjp$submit.pars$job.delay <- function(n,i) runif(1,1,3)

This works, but I think it would be nicer to have full control of the submitJobs parameters when creating the BatchJobsParam object, as well as to have documentation of how to do this in `?BatchJobsParam`

Alejandro

biocparallel • 918 views
ADD COMMENT
2
Entering edit mode
@martin-morgan-1513
Last seen 10 weeks ago
United States

I added conf.pars, reg.pars, and submit.pars arguments to the BatchJobs constructor as an alternative way to communicate with BatchJobs in BiocParallel version 1.5.18. Please let me know if there are problems; I'm not in the habit of using BatchJobs.

ADD COMMENT

Login before adding your answer.

Traffic: 776 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6