JuliaAI / JuliaAI/MLJModelInterface.jl
Expected behavior for repeated `fit!` calls
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Just wondering what the right strategy is for warm starts. What is the correct behavior for calling fit! on a machine twice? Here, I assume that the model has an $N$ parameter controlling the number of optimization steps:
model = Regressor(N=N)
mach = machine(model, X, y)
fit!(mach)
fit!(mach) # what happens here?
- Warm start; runs for another $N$ steps from where it left off.
- Warm start; runs for $0$ steps from where it left off. In other words, the user would need to increase $N$ if they want to replicate the behavior of (1)
fit!(mach) mach.model.N += N fit!(mach) - Cold start; resets the search state and runs for $N$ steps. Perhaps you need to use an
update!function for explicit warm starts (in which case 1 and 2 would require usingupdate!instead)
Right now, SymbolicRegression.jl is doing 2. But I'm not sure about this. Pinging @ablaom for tips.
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 examining the fit! entry point and the existing repeated-call behavior described for SymbolicRegression.jl. Determine and document the intended warm-start contract for a second fit!, including how the N parameter should behave; no specific files or tests are named in the issue.
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
- 25/100