scikit-learn / scikit-learn/scikit-learn

XGBRegressor is not working with wrapping `MultiOutputRegressor(StackingRegressor())` and `MultiOutputRegressor(VotingRegressor())`

Open
#33,933 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs Reproducible Code
Dominant language
Python
Stars
67.3k
Forks
27.4k
Avg merge
1d 15h
Merged PRs (30d)
58

Description

[!WARNING]
This issue is not yet ready for a PR. If you are interested in contributing to scikit-learn, please have a look at our contributing guidelines, and in particular the sections for new contributors and the "Needs triage" label.

Describe the workflow you want to enable

XGBRegressor is working well with StackingRegressor() and VotingRegressor() but when I try MultiOutputRegressor(StackingRegressor()) and MultiOutputRegressor(VotingRegressor()) it return error: ValueError: The estimator XGBRegressor should be a regressor.

Could we upgrade the MultiOutputRegressor() for this case? Thanks!

Describe your proposed solution

upgrade the MultiOutputRegressor()

Describe alternatives you've considered, if relevant

No response

Additional context

No response

Contributor guide

Open the contributing guide

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 by reproducing the reported workflow using MultiOutputRegressor with StackingRegressor and VotingRegressor around XGBRegressor, then inspect the estimator validation involved in the ValueError. Done should mean both wrapped workflows are accepted without the error and have regression tests covering them.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, scikit-learn
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.