Expected behavior for repeated `fit!` calls
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- julia
- Domain
- machine-learning
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.
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.
- Dominant language
- Julia
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from JuliaAI/MLJModelInterface.jl
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaAI/MLJModelInterface.jl#212 · 26 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
JuliaAI/MLJModelInterface.jl#209 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
JuliaAI/MLJModelInterface.jl#208 · 2 comments ·
-
next major release
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaAI/MLJModelInterface.jl#189 ·
-
next major release
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaAI/MLJModelInterface.jl#173 · 1 comment ·
All issues in JuliaAI/MLJModelInterface.jl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Sienna-Platform/PowerSimulations.jl#1737 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FluxML/Optimisers.jl#254 ·
-
Minor: floodplain warning percentage, scalar output error message and a never-true identity checkOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JuliaAI/MLJTransforms.jl#101 ·
Maintainers usually reply within 1 day
-
@contents blocks fail to render on Julia 1.14Possibly taken @sbfnk claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LuxDL/DocumenterVitepress.jl#410 ·