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

Add warnings about using the GLM alpha array internal grid #7500

Closed
exalate-issue-sync bot opened this issue May 11, 2023 · 2 comments
Closed

Add warnings about using the GLM alpha array internal grid #7500

exalate-issue-sync bot opened this issue May 11, 2023 · 2 comments

Comments

@exalate-issue-sync
Copy link

We allow the user to do an internal grid search for GLM alpha by passing an array instead of a float.

When calling GLM with an array of alpha (what we do in AutoML), a cold start is used at each new alpha value. However, with the same alpha value, lambda-search will have warm start (making use of the previous coefficient). You can actually pass an array of alphas directly to alpha in GLM, however, this is not documented.

Add the warning if user passes alpha to H2O Grid w/ GLM to warn them this is a less efficient way to search alpha

{code:r}> g <- h2o.glm(y = "Species", training_frame = as.h2o(iris), lambda_search = TRUE, alpha = c(0.0, 0.5)){code}

The documentation-only version of this ticket is here: [https://h2oai.atlassian.net/browse/PUBDEV-8171|https://h2oai.atlassian.net/browse/PUBDEV-8171|smart-link]

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Details

Jira Issue: PUBDEV-8150
Assignee: Wendy
Reporter: Erin LeDell
State: Resolved
Fix Version: 3.32.1.4
Attachments: N/A
Development PRs: Available

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

Linked PRs from JIRA

#5511

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