Add iteration deletion from `Runpath` to `runconfig`
- Dominant language
- Python
- Stars
- 161
- Forks
- 140
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 138
Description
We should allow users to delete specified iterations (e.g iter-1 and iter-2) from the `Runpath` post evaluation. This should be set via iteration specific checkboxes/list of iterations (CLI). Removing it could reduce amount of space used on the scratch disk, keeping only the necessary files for QC.
Should be opt-in and not opt-out, do not want to risk ruining runs for the users
Contributor guide
Research direction
Start by locating the runconfig CLI handling for Runpath and the post-evaluation lifecycle. Trace how iteration-specific options are parsed and how scratch-disk files are retained, then define completion as an explicit opt-in selection that removes only the requested iterations while preserving necessary QC files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100