-
Notifications
You must be signed in to change notification settings - Fork 256
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.
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
Improve the reporting of invalid input values #145
Comments
This See section "Values and Intervals" here: And if you think that this restriction is not appropriate for the particular application scenario, then you should:
TLDR: The JPMML-Evaluator library is behaving 100% correctly, by preventing you from using a model with invalid input values. |
My takeaway is that perhaps there should be a new, special-purpose exception type for capturing this situation. The name of the current exception type reads as |
thank you so much. maybe it's not that often to see unseen data on oot dataset |
When convert lightgbm to pmml, there exist error like:
expected: 'DOUBLE', got: '4.0'. error: org.jpmml.evaluator.InvalidResultException
this happen because the pmml file have structure like
<DataField name="feature_name" optype="continuous" dataType="double">
<Interval closure="closedClosed" leftMargin="0.0" rightMargin="3.0"/>
</DataField>
just remove this part <Interval closure="closedClosed" leftMargin="0.0" rightMargin="7034.5"/>, then it will work fine
The text was updated successfully, but these errors were encountered: