-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support SLURM array jobs in babs-submit
#175
Comments
@djarecka my memory is fuzzy here - did you at one point start working on this? I remember talking about it |
I think at the end we decided to leave it for later, so I haven't added. But I would be happy to take a look |
Hi @djarecka, I'd like to work on adding SLURM array job submission to BABS. @mattcieslak mentioned that you worked on this before, so I want to reach out to see what's the best way for us to work together, maybe I can start by learning from the branch you were working on for this issue? |
Hi @tientong98 , thanks for reaching. I've been just checking my old branches. And it doesn't look like the work was ever finished, and it was before some other changes to the main babs code, so it's hard to understand changes between branches.. If you want to work on this, perhaps we can have a quick chat next week, or I can point you on github to the places I believe should be changed. And if you already started working, I'm happy to review and test. Let me know what would work best for you! |
if people use check status -- grep subid and sesid (because log files don't have this appended in file name) babs.py: babs_status: utils.py: create_job_status_csv cli.py: |
Summary
It looks like BABS currently submits a separate job for each subject/session, but an array job would be nice. Proposed by @mattcieslak.
The text was updated successfully, but these errors were encountered: