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

Restructure algorithm pages parameters section in User Guide #7600

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

Restructure algorithm pages parameters section in User Guide #7600

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

Comments

@exalate-issue-sync
Copy link

I have some ideas about how to help restructure the parameters that we list on the algorithm user guide pages (we can discuss more and then refine this ticket...). There's a lot of duplication between the algorithm pages, and currently we can't tell what parameters are common algo params vs hyperparams that are unique to the specific algorithm (e.g. sample_rate, mu_factor, etc).

We could break the param lists on the page into two groups: common algo params & algo-specific params.

We could also consider moving all the common algo params to their own user guide page and then we can keep one copy of them. I think what's the most interesting when a user visits an algo page is how to tune that particular algorithm, not the generic data/algo params like: x, y, training_frame, nfolds, seed, etc. This would also make the user guide pages shorter.

Lastly, the order of the common algo params are a bit weird (starting with optional model_id). We should do a more sensible ordering (e.g. http://docs.h2o.ai/h2o/latest-stable/h2o-r/docs/reference/h2o.xgboost.html)

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Details

Jira Issue: PUBDEV-8049
Assignee: hannah.tillman
Reporter: Erin LeDell
State: Resolved
Fix Version: 3.40.0.4
Attachments: N/A
Development PRs: Available

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

@h2o-ops h2o-ops closed this as completed May 14, 2023
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

2 participants