Request: Separate Out Resampling Strategies Interface
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 163
- Forks
- 46
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 5
Description
I'd like to use the interface for resampling strategies separately from MLJBase in ParetoSmooth.jl, but MLJBase is a pretty big dependency to add for such a small interface. Would it be a good idea to separate out an MLJResampling package similar to what's been done with LossFunctions.jl?
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 reviewing the resampling-strategy interface in MLJBase.jl and how ParetoSmooth.jl consumes it. Compare the existing LossFunctions.jl split and determine the package boundary, dependencies, and migration path; done means a concrete decision on whether an MLJResampling package should be created.
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
- 20/100