Updated handling of missing values with LightGBM, and added ability to use (0) as missing value#4695
Updated handling of missing values with LightGBM, and added ability to use (0) as missing value#4695mstfbl merged 24 commits intodotnet:masterfrom
Conversation
|
The current CI tests are failing due to the current generated netcoreapp core_manifest.json not exactly matching with the generated baseline core_manifest.json. The difference here is caused by the newly added
|
|
@mstfbl: We may want to document how to update the I think the method is to unskip the machinelearning/test/Microsoft.ML.Core.Tests/UnitTests/TestEntryPoints.cs Lines 230 to 256 in 97c4533 |
|
Another option is to run In reply to: 579335552 [](ancestors = 579335552) |
ganik
left a comment
There was a problem hiding this comment.
Pls try to run old LightGBM model (trained without your changes) with your new code. Baseline numbers should be the same.
Fixes #4681 , and also adds the ability to use the numerical value (0) as missing value with LightGBM. In addition, I've also updated the baseline results for LightGbm as it is normal for them to change with
CursOpt.AllFeatures, and all added a unit test checking that a previously trained LightGBM model with theCursOpt.Featuresflag produces the baselines it did before.