-
Notifications
You must be signed in to change notification settings - Fork 28
Inconsistent handling of gres in profiles #248
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
Comments
Interesting observation - I am sorry, we are still putting some work in the documentation. Please try not to nest this string, so I will put an extra check and a more informative error message in the upcoming release. |
Removing the extra single quotes leads to parsing error and suggestion to add them. As far as I know the gpu/gpus parameter uses different mechanism than Slurm GRES so it won't work when using GRES. Just to confirm I tried gpu switch and GRES is not requested (no GPU is requested). |
I will look into this. Regarding the |
Sorry for late reply, I was on holidays. The cluster is running Slurm 23.11.3. It is possible that Can I somehow see what command is Snakemake using for submission? Some parameters are visible when running rules, but they don't look like params for |
sure: I think, I found a remedy for not requiring nested strings in profiles: snakemake/snakemake#3506 |
Uh oh!
There was an error while loading. Please reload this page.
Software Versions
Snakemake 9.1.3
snakemake-executor-plugin-slurm 1.1.0
Describe the bug
This works
but with
gres
set in a rule, in the same profile filefollowing error appears
Aside from failing submission, the message suggests to use format that is already used.
More details in case parameters interfere with each other
The text was updated successfully, but these errors were encountered: