You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an actual issue. I just wanted to share that I have looked at qme and it looks as if it would plug a whole that I have not attempted to fill in https://github.com/datalad/datalad-htcondor. This is a (presently) stalled prototype of a DataLad extension to execute datalad run style commands via HTCondor, and have the execution graph be reflected in the Git history of a dataset repository.
When I get back to this project, I will make a concrete attempt to use qme for the job tracking aspect. If my understanding of the system is somewhat valid, this might yield an HTCondor executor for qme.
The text was updated successfully, but these errors were encountered:
This sounds great! If you want some help, if you write out the flow that you'd want (and actions) I can give a shot at a skeleton, although I don't have a cluster that I could test on. I'll point you to this guide https://vsoch.github.io/qme/tutorials/create-executor/ for the thinking process I went through when adding the slurm executor.
This is not an actual issue. I just wanted to share that I have looked at
qme
and it looks as if it would plug a whole that I have not attempted to fill in https://github.com/datalad/datalad-htcondor. This is a (presently) stalled prototype of a DataLad extension to executedatalad run
style commands via HTCondor, and have the execution graph be reflected in the Git history of a dataset repository.When I get back to this project, I will make a concrete attempt to use
qme
for the job tracking aspect. If my understanding of the system is somewhat valid, this might yield an HTCondor executor forqme
.The text was updated successfully, but these errors were encountered: