Limited support for slurm? #2329
Answered
by
jianxinwang
jianxinwang
asked this question in
Q&A
Replies: 2 comments 1 reply
-
Could you paste some sample code you were using? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I got the solution. I found I can put the other slurm parameters as a
single line in clusterOptions. Thanks!
Jason
…On Fri, Sep 17, 2021 at 4:13 PM Josef ***@***.***> wrote:
Could you paste some sample code you were using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2329 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACX6JW62T4JVAQKYD5UEKATUCOOP5ANCNFSM5EHZDEWA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
bentsherman
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our HPC uses the Slurm job schedular. However, when I looked at the documentation for slurm in the executor section, it has very basic parameters we can set. Our HPC slurm setup uses the additional parameters like "clusters", "account", "constraints", "qos" other than just the "partition" parameter (which called queue in nextflow). I put these extra parameters in the nextflow config file and tried to run a nextflow command. It did not work because when examining the resultant .command.run script, these extra parameters did not show up, only the basic slurm parameters. I wonder if this is caused by putting these parameters in the wrong location or current version of nextflow lacks the support for these parameters? Please help. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions