JuliaAI / JuliaAI/MLJIteration.jl
Add automatic tracking of validation loss and an optional recommendation
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 12
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I can access training_losses from report(mach) but I was surprised that there is no validation_losses (although these are certainly computed with a holdout or resampling strategy).
I understand that I can use callbacks for this but it felt asymmetric (and less friendly) to only find training_losses but no num_epochs_finished (although it can be derived from the log anyway) or validation_losses.
As for the optional recommendation, currently the argument controls allows two types of functionality:
- Specifying conditions to stop training
- Specifying callbacks to call while training
I think it's more intuitive to have two separate arguments. Maybe stop_conditions=[...] for the former and callbacks=[...] for the latter.
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 at the report(mach) entry point and inspect how training_losses and num_epochs_finished are assembled. Trace the holdout or resampling path and the controls handling for stopping conditions and callbacks. Done means the reporting additions and the proposed controls API separation have defined behavior and are covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- api, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100