[SW-2559] Expose Scoring History and Variable Importances on H2OMOJOModel #2525
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michalkurka
reviewed
May 7, 2021
...neration/src/main/scala/ai/h2o/sparkling/api/generation/common/AlgorithmConfigurations.scala
Outdated
Show resolved
Hide resolved
michalkurka
reviewed
May 7, 2021
michalkurka
reviewed
May 7, 2021
|
When people are training CV models, how do they have access to scoring history of the CV models? Also how do they access CV metrics, training metrics and validation metrics? |
As discussed, it's not currently possible
|
mn-mikke
commented
May 11, 2021
| val rows = (0 until table.rows()).map { rowId => | ||
| val rowData = (0 until table.columns()).map { colId => | ||
| table.getCell(colId, rowId) match { | ||
| case str: String if table.getColTypes()(colId) == ColumnType.INT => Integer.parseInt(str) |
There was a problem hiding this comment.
IMHO, this should be handled on H2O-3 side. I'm not sure about the impact of the eventual change
michalkurka
approved these changes
May 24, 2021
mn-mikke
added a commit
that referenced
this pull request
May 24, 2021
…odel (#2525) * [SW-2559] Expose Scoring History and Variable Importances on H2OMOJOModel * Deprecate variable importances on H2ODeepLearning * Rename variable importances to feature importances * Extend documentation * Fix deserialization problem * spotless apply * Fix python tests and deprecation on DeepLearningMOJOModel * fix python tests * fix R tests * typo * fix R tests * spotless apply * null handling (cherry picked from commit 3fab572) # Conflicts: # api-generation/src/main/scala/ai/h2o/sparkling/api/generation/common/AlgorithmConfigurations.scala
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira ticket: https://h2oai.atlassian.net/browse/SW-2559