combust/mleap
View on GitHubAutomate parity tests between scikit-learn and MLeap transformers
Open
#316 opened on Dec 19, 2017
0 comments (0 comments)2 reactions (2 reactions)0 assignees (0 assignees)Scala1,461 stars (1,461 stars)312 forks (312 forks)batch import
enhancementhelp wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- pythonscala
- Domain
- testingmachine learning
- Issue type
- test
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- Basic Scala knowledgeFamiliarity with scikit learnUnderstanding of MLeap
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- Investigate the existing test infrastructure in the MLeap repository (e.g., 'mleap core/src/test') to understand how tests are structured. Then design a script or test suite that compares the output of scikit learn transformers with MLeap transformers for a set of common transformations. Consider using a CI tool like GitHub Actions to run the parity tests automatically. Refer to any prior discussions or linked PRs that may provide context.