Fix missing type in lgbm regressor #488
Merged
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
janjagusch
force-pushed
the
fix-missing-type-in-lgbm-regressor
branch
from
c887262
to
aab0e17
Compare
Signed-off-by: Jan-Benedikt Jagusch <jan.jagusch@gmail.com>
janjagusch
force-pushed
the
fix-missing-type-in-lgbm-regressor
branch
from
aab0e17
to
978954e
Compare
|
@xadupre, if you have time, could you please take a look at this? 🙂 it's quite important, as the ONNX graph currently produces wrong predictions in some special cases. |
xadupre
approved these changes
Aug 16, 2021
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.
Fixed a bug, where the ONNX model would take a different path through the tree compared to the LGBM regressor when
tree_structure["missing_type"] == 'None' and float(tree_structure['threshold']) < 0.0.