rasbt / rasbt/mlxtend

stacking, named base models

Open
#641 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement
Dominant language
Python
Stars
5.2k
Forks
916
Avg merge
17h 31m
Merged PRs (30d)
4

Description

It would be nice if the base models in the stacking ensembles explicitly required names, similar to sklearn's Pipeline named_steps and ColumnTransformer. When all my base models are themselves pipelines, digging into the nest to find actual names becomes tedious. (Especially in the context of set_params and grid searches, where the default behavior requires things like pipeline-1__...: http://rasbt.github.io/mlxtend/user_guide/classifier/StackingCVClassifier/#example-3-stacked-cv-classification-and-gridsearch )

Maybe it's too late to try to change the API to require names as in ColumnTransformer, but perhaps as an optional parameter?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the stacking ensemble API, especially StackingCVClassifier, and compare its current parameter naming with sklearn Pipeline named_steps and ColumnTransformer. Review how set_params and grid searches currently address nested base models; done requires a decided required-versus-optional naming design and corresponding parameter paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, scikit-learn
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.