error when running with targets #250
-
|
I am not sure where to put this error message @wlandau @mschubert but I put it here first since I am running this in Sanger Institute's LSF Farm and perhaps @mschubert will be more familiar with LSF there? Steps to reproduce:
|
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
|
Can you reproduce the error with just options(clustermq.scheduler = "lsf", clustermq.template = "your_template.tmpl")
library(clustermq)
f <- function(x) x * 2
Q(f, x = seq_len(2), n_jobs = 1) |
Beta Was this translation helpful? Give feedback.
-
|
thanks a lot @wlandau! i think the issue might be clustermq config then? |
Beta Was this translation helpful? Give feedback.
-
|
I did specify These are the only four lines that produce the error above: |
Beta Was this translation helpful? Give feedback.
-
|
I think your Is not valid because you're (1) referencing a directory instead of a file, and (2) I'm not sure if LSF expands And aren't there |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @mschubert ! by adding back the Could you give a bit more guidance on how to modify the template? I do not quite understand how the syntax with curly brackets works so if there are documentations on that (could not find in the pkgdown page), it will be great! |
Beta Was this translation helpful? Give feedback.
-
|
@liutiming The wildcard words inside the double curly-brackets will get "filled in" when Let's take Here is how you would control memory via tar_option_set(
resources = list(memory = 1000) # this will replace {{ memory }}
)
tar_make_clustermq()With the issue you were having: Lastly, the convention for specifying LSF directives using Hope this is helpful. |
Beta Was this translation helpful? Give feedback.
-
|
@matthewstrasiotto immensely helpful. thank you! |
Beta Was this translation helpful? Give feedback.
@liutiming The wildcard words inside the double curly-brackets will get "filled in" when
clustermqsubmits the jobs using this template. The values coming after the vertical pipe (|) are fall-back default values.Let's take
#BSUB-M {{ memory | 4096 }}as an example, if you do not pass amemoryvalue when callingclustermq(either directly or indirectly viatargets), then it will use 4096MB as the memory for your jobs.Here is how you would control memory via
targets:With the issue you were having:
BSUB-o {{ log_file | ~/clustermq_log/ }}, you can either specify the path to a file fo…