MLBazaar / MLBazaar/MLPrimitives
Make `score_pipeline` more flexible
Open
Nobody has claimed this yet.
new feature
- Dominant language
- Python
- Stars
- 70
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Provide more control over the mlprimitives.evaluation.score_pipeline function in order to allow:
- Defining HyperParameters
- Passing an MLPipeline instance or dict
- Using a different metric
Contributor guide
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 locating the mlprimitives.evaluation.score_pipeline function and read its current arguments and callers. Define how it should accept hyperparameters, an MLPipeline instance or dict, and an alternate metric; done means all three requested forms work without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100