sokrypton / sokrypton/ColabFold
checkpointing in job submissions
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 2.9k
- Forks
- 747
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am trying to add some sort of checkpointing to my slurm scripts so I could rerun the script and the colabfold can run from where it got dropped off due to time limits or resources. How can I do that?
Thank you in advance!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report concerns checkpointing in Slurm scripts used to run ColabFold, but it names no repository files, tests, or entry points. Start by locating the job-submission workflow and existing Slurm guidance; done would require an agreed way to resume interrupted runs and documentation or tests showing that behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics, hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100