Logging data in between algorithm iterations
Open
Nobody has claimed this yet.
infrastructure
- Dominant language
- Rust
- Stars
- 4.7k
- Forks
- 334
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
It'd be nice to have a way of logging information between each step when fitting an iterative algorithm for debugging purposes. For algorithms that use argmin we can simply call add_observer on Executor.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the iterative algorithm implementations and the Executor integration described in the issue, then read Executor.add_observer for the existing observation path. Determine which algorithms need the facility and how completion is verified by observing information between fitting steps; the issue names no files or tests, so those entry points must be identified first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100