JuliaAI / JuliaAI/LearnDataFrontEnds.jl
Expand front ends to support specification of per-observation weights.
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In MLJModelInterface.jl weights appear last, as in (X, y, w) (supervised case) but I'm inclined here to use (X, w, y), so that the target, when present, is always last. This is because the fallback for LearnAPI.target grabs the last element of a tuple.
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 reading the front-end handling in LearnDataFrontEnds.jl and the referenced MLJModelInterface.jl convention, then inspect the LearnAPI.target fallback. Confirm how tuple inputs are currently interpreted and identify the tests covering supervised inputs. Done means per-observation weights are accepted with the target remaining last, with the existing behavior preserved where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100