estimators
Route feature-importance and learning-curve requests to scikitplot.estimators.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- estimators
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Route feature-importance and learning-curve requests to scikitplot.estimators.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/api-reference.md2.3 KB
- 参考文档references/troubleshooting.md1.8 KB
- 参考文档references/workflows.md2.7 KB
- 脚本scripts/estimators_smoke.py1.5 KB
03 SKILL.md 正文
Estimators
Use this sub-skill for the estimator-oriented plots in scikitplot.estimators: feature importances and learning curves.
Route here
- Plot feature importances from a fitted estimator that exposes
feature_importances_. - Plot learning curves from an estimator plus
X,y, CV choices, and scoring settings. - Reuse or compose Matplotlib axes with
ax=; both functions return the axes they drew on. - Validate the route quickly with
scripts/estimators_smoke.py.
Reroute
- Confusion matrix, ROC, precision-recall, KS, calibration, cumulative gain, lift, or silhouette:
../metrics/SKILL.md. - Elbow-curve workflows or clusterer-specific routing:
../clustering/SKILL.md. - Bound-method wrappers from the legacy factory layer, including injected estimator methods:
../legacy-factories/SKILL.md. - PCA or other dimensionality-reduction plots: not handled here.
Start fast
- Confirm the estimator contract.
plot_feature_importancesrequiresfeature_importances_.plot_learning_curvepasses an estimator throughsklearn.model_selection.learning_curve.
- Pick the right options.
orderaccepts onlyascending,descending, orNone.cv,shuffle,random_state,train_sizes,n_jobs, andscoringare forwarded tolearning_curve.
- Reuse axes explicitly when composing figures.
- Run the smoke script for a tiny deterministic check:
python scripts/estimators_smoke.py
References
references/api-reference.mdreferences/workflows.mdreferences/troubleshooting.mdscripts/estimators_smoke.py
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).