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.

Sign up for GitHub

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

Jump to bottom

Imported MOJO produces incorrect predictions for non-AUTO categorical encodings #7423

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

Imported MOJO produces incorrect predictions for non-AUTO categorical encodings #7423

exalate-issue-sync bot opened this issue May 11, 2023 · 2 comments
Labels
fixVersion/3.32.1.5

Comments

@exalate-issue-sync
Copy link

 GenericModel (=imported MOJO) doesn’t know anything about categorical encodings - it doesn’t know the original names/domains, it doesn’t know the categorical encoding used and it doesn’t know the associated encoding parameters (eg max_cat in enum limited case).
@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Details

Jira Issue: PUBDEV-8230
Assignee: New H2O Bugs
Reporter: Michal Kurka
State: Resolved
Fix Version: 3.32.1.5
Attachments: N/A
Development PRs: Available

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

Linked PRs from JIRA

#5564
#5589

@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
Assignees
No one assigned
Labels
fixVersion/3.32.1.5
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@h2o-ops