New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clusterOptions does not work with CLI flags (LSF executor) #4935
Comments
It is because the abstract grid executor assumes the cluster options are provided as key-value pairs: nextflow/modules/nextflow/src/main/groovy/nextflow/executor/AbstractGridExecutor.groovy Lines 95 to 116 in 7c9d965
So you can probably make clusterOptions = { "-g /${_queue_group} -app ${params.fast_track ? params.lsf_fast_track_profile : task.process.tokenize(':')[-1].toLowerCase()} -sp ${params.hpc_priority} -P ${params.lsf_project_name} -rn ''" } |
@pditommaso what if we allow clusterOptions to be a list of strings, then it becomes clear how to map the options to the directive lines: clusterOptions = { [
"-g /${_queue_group}",
"-app ${params.fast_track ? params.lsf_fast_track_profile : task.process.tokenize(':')[-1].toLowerCase()}",
"-sp ${params.hpc_priority}",
"-P ${params.lsf_project_name}",
"-rn" ] } |
It makes sense |
Bug report
when specigying a clusterOptions which includes a flag the Grid executor header is constructed wrongly by nextflow
e.g profile.config :
results in the following BSUB command (LSF executor)
Expected behavior and actual behavior
I would expect flags (keys with no values) to be correctly rendered in the BSUB option lists
Steps to reproduce the problem
(Provide a test case that reproduce the problem either with a self-contained script or GitHub repository)
Program output
(Copy and paste here output produced by the failing execution. Please highlight it as a code block. Whenever possible upload the
.nextflow.log
file.)Environment
$SHELL --version
)Additional context
(Add any other context about the problem here)
The text was updated successfully, but these errors were encountered: