-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Support offsets in the Stacked Ensemble metalearner #11793
Comments
Erin LeDell commented: Note that potential work-around, adding {{offset_column}} to {{metalearner_params}}, does not work because we do not currently copy the offset column to the level-one frame (thus its not available to use in metalearning and it fails). {quote}Error: water.exceptions.H2OModelBuilderIllegalArgumentException: Illegal argument(s) for GLM model: metalearner_AUTO_StackedEnsemble_model_R_1582665555956_1952. Details: ERRR on field: _offset_column: Offset column 'wts' not found in the training frame{quote} |
Erin LeDell commented: Here’s some R code for a test: {noformat}set.seed = 123 x <- 3:length(colnames(hdata)) works for a regular GLMhh3 <- h2o.glm(x = x, Train & Cross-validate a GBMgbm <- h2o.gbm(x = x, Train & Cross-validate a RFrf <- h2o.randomForest(x = x, stack_model <- h2o.stackedEnsemble(x = x, |
Tomas Fryda commented: This is included in PR for {{weights_column}} ([https://0xdata.atlassian.net/browse/PUBDEV-4916|https://0xdata.atlassian.net/browse/PUBDEV-4916|smart-link] ). |
JIRA Issue Migration Info Jira Issue: PUBDEV-4915 |
We don't support using offsets (offset_column) in Stacked Ensemble. You can use offsets in the base learners, but Stacked Ensemble metalearner is hardcoded and doesn't honor that. We need to check:
training_frame
for Stacked Ensemble and then we should use it automatically.The text was updated successfully, but these errors were encountered: