Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow base models have different training_frame in blending mode #9136

Closed
exalate-issue-sync bot opened this issue May 12, 2023 · 4 comments
Closed

Allow base models have different training_frame in blending mode #9136

exalate-issue-sync bot opened this issue May 12, 2023 · 4 comments

Comments

@exalate-issue-sync
Copy link

It seems that base models in ensemble must have the same training_frame, but actually this is not required by blending mode. Adding this feature might increase diversity of base models.

@exalate-issue-sync
Copy link
Author

Sebastien Poirier commented: Currently, there is just a validation when preparing the SE model ensuring that the training frame is same as for base models, this can be easily restricted to stacking mode.

@exalate-issue-sync
Copy link
Author

Erin LeDell commented: [~accountid:5b153fb1b0d76456f36daced] In CV-model, we can also allow the training frames to have different columns (though they must have the same rows). It looks like this was already implemented here (but if so, i don’t know why we have this current ticket): [https://0xdata.atlassian.net/browse/PUBDEV-4679|https://0xdata.atlassian.net/browse/PUBDEV-4679|smart-link] so if not, it might make sense to add this at the same time.

@exalate-issue-sync
Copy link
Author

Sebastien Poirier commented: [~accountid:557058:afd6e9a4-1891-4845-98ea-b5d34a2bc42c] there’s a difference

For both CV and blending, we require {{response_column}} to be present in all training frames.

For CV, we require only that all training frames have the same number of rows.

For blending, this last constraint is removed.

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Migration Info

Jira Issue: PUBDEV-6494
Assignee: Sebastien Poirier
Reporter: Zhifeng Wang
State: Resolved
Fix Version: 3.26.0.8
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#3910

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant