-
Notifications
You must be signed in to change notification settings - Fork 5
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
Record job and DB ID in slurm job #40
Comments
Hi @janosh Thanks for the question. Regarding qverbatim, indeed, it should be used as in your second example:
QResources is indeed meant to be used as a common object for specifying resources. Difficulty is that not all DRM's provide the same functionalities. This is why there is the scheduler_kwargs, allowing you to pass anything you want by yourself (through qverbatim in slurm). Now if comment were to be a commonly (and common) option in DRM's (well currently qtoolkit only supports PBS and slurm), we could add it to QResources. I'm not sure PBS has an "equivalent". Now maybe there is a different question to be raised in why you want to have the dbid in the comment and maybe there is a different way to do that (maybe in jobflow-remote) ? Open to discuss if needed. Pinging @gpetretto in case I said something wrong here :-) |
thanks @davidwaroquiers, that's very helpful! i wanted the DB ID in the comment to be able to map from the output of i'll still be using |
sbatch
has a handy--comment
that allows adding metadata to jobs:sbatch -h | grep comment --comment=name arbitrary comment
i'd like to use this to connect my slurm jobs back to jobs in the database either via their jobflow or their database ID. i saw there's no explicit support for
comment
inSlurmIO
:qtoolkit/src/qtoolkit/io/slurm.py
Lines 148 to 176 in e95110a
maybe
qverbatim
is meant as an escape hatch for situations like this? didn't find any docs on it. also not sure how to setqverbatim
. this raisesmaybe like this? didn't try yet but either way would be good to document how to pass
qverbatim
The text was updated successfully, but these errors were encountered: