enh: con-duct aggregate <paths or regex to info.json>
Open
- Dominant language
- Python
- Stars
- 12
- Forks
- 6
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 2
Description
The idea would be to look at multiple `duct` execution logs and give useful stats about them.
For example if running many jobs of mriqc with duct (1 per subject) it would be nice to see the peak memory usage for any of the executions, average, and maybe sum?
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by locating the con-duct command handling execution logs and the info.json data, then determine how multiple paths or regex matches would be selected. Done should include useful aggregate statistics across executions, including peak, average, and possibly total memory usage.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100