Maestro write/update status.csv and check for cancellation after every job step
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 161
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Currently the `status.csv` is not written (such as for synchronous login node jobs) until all of the first job step jobs are completed, nor can cancellation be issued or checked until that point. Proposed changes:
- Write `status.csv` immediately after the study graph is created
- Update `status.csv` after synchronous login node job are completed
- Additionally check for cancellation between synchronous login node jobs
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
No files or tests are named. Start by locating the workflow entry point that creates the study graph, writes status.csv, runs synchronous login-node jobs, and checks cancellation. Implement the three requested checkpoints, then verify that status.csv is created immediately, updated after synchronous jobs, and cancellation is checked between those jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100