Composite example from MLJ
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- julia
- Domain
- machine-learning
Research direction
Start by reading MLJ.jl's examples/composite_example and comparing it with the existing tutorials in this repository. Identify which parts should be added and verify the selected composite workflow runs as a tutorial; the issue does not specify a target file or exact scope.
Written by the indexing model from the issue text.
Description
Check this: https://github.com/alan-turing-institute/MLJ.jl/tree/master/examples/composite_example and possibly add bits of it
- Dominant language
- ReScript
- Stars
- 126
- Forks
- 19
- 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/DataScienceTutorials.jl
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
JuliaAI/DataScienceTutorials.jl#239 · 5 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
JuliaAI/DataScienceTutorials.jl#229 · 1 comment · 1 reaction ·
-
tutorial organization
Difficulty 3/5 1-2 days Newbie friendliness 35/100
JuliaAI/DataScienceTutorials.jl#228 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
testing
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in JuliaAI/DataScienceTutorials.jl
Similar issues
-
agent/scanner bug stage/010-actionable
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
torch-spyre/spyre-inference#1748 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
CausalForecaster fails with KeyError/IndexError on graphs that include the C nodePossibly taken @aryankalantri claimed this today. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Serialization] `load_state_dict_from_file` drops the device index of a `torch.device` map_locationPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
huggingface/huggingface_hub#5409 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
flashinfer-ai/flashinfer#9803 ·
Maintainers usually reply within 1 day