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

AutoML: define simplified modeling plan when max_models is enabled #7062

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

Comments

@exalate-issue-sync
Copy link

We should see {{max_models}} parameter as used mainly when user wants AutoML to be reproducible, it’s actually a requirement for this.

Another obvious requirement is that it’s not because user specifies {{max_models}} that we’re allowed to “waste” computation time.

Expected behaviour when user sets {{max_models = N}}:

  • train exactly N base models.
  • all base models are trained until convergence (except if {{max_runtime_per_model}} is also set explicitely).
  • the {{N}} models are distributed between
    ** default models first (same order as default modeling plan)
    ** various grids
  • no intermediate SE model trained
  • 2 default SE are trained after all base models:
    ** Best of Each Algo, using GLM metalearner with lambda search.
    ** All Models, using GLM metalearner with lambda search.
  • 1 monotonic SE trained if conditions are satisfied.
  • if user ALSO specifies {{max_runtime_secs}}, then AutoML should stay MAINLY reproducible, which means that the time budget is used ONLY to interrupt the last step, not as a time constraint during individual model training. This also means that in this case, the last model interrupted by this time cap should be completely thrown away.
@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Details

Jira Issue: PUBDEV-8613
Assignee: Sebastien Poirier
Reporter: Sebastien Poirier
State: Resolved
Fix Version: 3.36.1.1
Attachments: N/A
Development PRs: Available

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

Linked PRs from JIRA

#6116

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