CV GBM: Update cv ntrees in summary table based on best score

[exalate-issue-sync]

[https://h2oai.atlassian.net/browse/PUBDEV-8185|https://h2oai.atlassian.net/browse/PUBDEV-8185|smart-link]

The linked story changed how the ntrees of the main model and cv model are selected. I noticed that the ntrees in the cross-validation model summary tables is still based on how many trees were built, and hasn’t been updated to reflect that some trees were removed due to a better score occurring with fewer. I think it would make sense to update this value as well, since it potentially could be pretty different depending on how often the models are being scored.

[exalate-issue-sync]

Zuzana Olajcová commented: Resolved in [https://github.com//pull/6213|https://github.com//pull/6213|smart-link]

[h2o-ops]

JIRA Issue Details

Jira Issue: PUBDEV-8625
Assignee: Zuzana Olajcová
Reporter: Paul Donnelly
State: Resolved
Fix Version: 3.36.1.3
Attachments: N/A
Development PRs: Available

[h2o-ops]

Linked PRs from JIRA

#6213