Helmholtz-AI-Energy / Helmholtz-AI-Energy/propulate
Propulator.propulate refactor
Open
Nobody has claimed this yet.
maintenance
- Dominant language
- Python
- Stars
- 46
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
- Having three copies of the same function that are slightly different is annoying to maintain.
- In the current structure parameters that are not needed have to be passed. E.g. multi-rank sub workers, do not need the checkpoint file handle.
- How do we measure evaluation times properly across restarting from a checkpoint?
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
Start at the Propulator.propulate entry point and locate the three slightly different function copies mentioned in the issue. Trace how parameters, checkpoint handles, and evaluation timing are handled for multi-rank workers and checkpoint restarts. Done means the duplicated logic and unnecessary parameters are addressed, with a clear approach to measuring evaluation time across restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100