JuliaAI / JuliaAI/IterationControl.jl
Should a history of losses and training losses be explicity returned?
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 25
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently the workflow is to define an external variable and use the "callback" control WithLossDo - but perhaps there's an argument for collecting a history of the loss (and training loss and iteration count?) and returning these.
See also this discussion.
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 reviewing the existing WithLossDo callback control and the linked MLJ.jl issue 793 discussion. Clarify whether loss, training loss, and iteration counts should be returned, and define an agreed API and completion criteria before identifying implementation and test locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100