microsoft / microsoft/winml-cli
[Task] tabular-classification model support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 50
Description
Overview
Tabular classification models predict a categorical label from structured (tabular) data — rows of numeric and categorical features. These models are heavily used in enterprise and data analytics workflows. Unlike vision/NLP models, they typically use gradient-boosted tree or MLP architectures (e.g. XGBoost-backed ONNX exports, TabNet, FT-Transformer).
Target: top 2–8 models by HuggingFace downloads (>2k) covering representative architectures and business domains.
Agent Scenarios
- Risk / fraud detection agent: classify financial transactions as fraudulent or legitimate using structured account and transaction features
- Customer churn prediction agent: predict likelihood of customer churn from CRM feature tables to trigger retention workflows
- Medical diagnosis agent: classify patient records against structured clinical features (lab values, vitals, demographics)
- Lead scoring agent: rank and classify sales leads from CRM attributes to prioritize outreach
ModelKit Integration
Models must pass the full wmk pipeline on all EPs:
wmk config → wmk build (ONNX export) → wmk perf → wmk eval
Acceptance Criteria
- Identify top 2–8 tabular-classification models (>2k downloads) and add to model list
- All selected models pass
wmk perfon CPU EP - All selected models pass
wmk evalwith tabular dataset
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
No source file or test is named. Start by locating the model list, identify 2–8 tabular-classification models with more than 2k Hugging Face downloads, and run the listed wmk config, build, perf, and eval commands. Done means the selected models are listed and pass CPU performance and tabular-dataset evaluation.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100