Update documentation regarding AUTO option for the family parameter of GLM

[exalate-issue-sync]

In PUBDEV-7444 AUTO option for the family parameter of GLM was introduced. This needs to get documented, possibly in the following way:

in https://docs.h2o.ai/h2o/latest-stable/h2o-docs/data-science/gam.html and in https://docs.h2o.ai/h2o/latest-stable/h2o-docs/data-science/glm.html:

in family part, lines to be added:

If the family is AUTO,

• and the response is Enum with cardinality = 2, then the family is automatically determined as binomial
• and the response is Enum with cardinality > 2, then the family is automatically determined as multinomial
• and the response is numeric (Real or Int), then the family is automatically determined as gaussian

in link part, lines to be added:

If the family is AUTO,

• and link is not specified, then link is determined as default_family (default for the family to which AUTO is determined)
• and link is specified, then if specified link is compatible with the family to which AUTO is determined, then this link is used. Otherwise, error message is thrown, stating that AUTO for underlying data requires different link + list of possible compatible links.
• The list of supported links for family = AUTO:

If the response is Enum with cardinality = 2, then Logit is supported

If the response is Enum with cardinality > 2, then only Family_Default is supported (This defaults to multinomial.)

If the response is numeric (Real or Int), then Identity, Log and Inverse are supported.

in https://docs.h2o.ai/h2o/latest-stable/h2o-docs/data-science/algo-params/family.html :

in family part, lines to be added:

AUTO: can fall to three cases based on the response:

• if the data is Enum with cardinality = 2, then the family is automatically determined as binomial
• if the data is Enum with cardinality > 2, then the family is automatically determined as multinomial
• if the data is numeric (Real or Int), then the family is automatically determined as gaussian

[h2o-ops]

JIRA Issue Migration Info

Jira Issue: PUBDEV-7648
Assignee: hannah.tillman
Reporter: Zuzana Olajcová
State: Resolved
Fix Version: 3.30.1.1
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#4769