Compatibility bottlenecks in the MLJ Model Registry
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- julia
- Domain
- machine-learning
Research direction
Start with the edited ] status --outdated -m output in this issue and investigate the listed packages, especially the compatibility paths involving Optim, LineSearches, NLSolversBase, and SymbolicRegression. Check whether the outdated constraints can be resolved or whether they are blocked by the planned SymbolicRegression v2 work; done means the registry no longer has the identified blocking incompatibilities or the remaining blockers are documented.
Written by the indexing model from the issue text.
Description
There are are few packages in the registry whose compatibility updates may block use with other models the registry. This is an edited list of the output of ] status --outdated -m for the model registry after an update today. I have omitted .jll packages. The most concerning are packages not updating to latest Optim.
Be great if we could get help chasing some of these down.
- ⌅ [7317a516] DynamicDiff v0.2.1 (<v0.3.1): SymbolicRegression
- ⌅ [a40a106e] DynamicExpressions v1.10.4 (<v2.5.2): DynamicDiff, SymbolicRegression
- ⌃ [d3d80556] LineSearches v7.5.1 (<v7.6.0)
- ⌅ [d41bc354] NLSolversBase v7.10.0 (<v8.0.0): LineSearches, Optim
- ⌅ [429524aa] Optim v1.13.3 (<v2.0.1): MLJLinearModels, SymbolicRegression
- ⌅ [92933f4c] ProgressMeter v1.10.2 (<v1.11.0): SymbolicRegression
- ⌅ [68821587] Arpack_jll v3.5.2+0 (<v3.9.2+0): Arpack
The maintainer of SymbolicRegression is aware of the issues here; v 2.0 of that package aims to resolve these.
- Dominant language
- Julia
- Stars
- 82
- Forks
- 29
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 2
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/MLJModels.jl
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
JuliaAI/MLJModels.jl#591 · 2 comments · 1 reaction ·
-
Review the MLJ model interfaces at RAPIDS.jl for possible inclusion in model registryMay be free again @ablaom claimed this 1684 days ago, and no pull request is open. Open
JuliaAI/MLJModels.jl#454 · 2 reactions · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
JuliaAI/MLJModels.jl#392 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
JuliaAI/MLJModels.jl#368 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
JuliaAI/MLJModels.jl#322 · 3 reactions ·
All issues in JuliaAI/MLJModels.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 ·