-
Notifications
You must be signed in to change notification settings - Fork 255
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
Question: multipleModelMethod="max" when multiple classes have max #53
Comments
The And I think the following is a correct implementation of the spec:
Here are my unit tests: The important detail is that the tie resolution is a two step process. First, if there is more than one winner, then you compute the average of their probability distributions. Second, if there is still more than winner (eg. categories Feel free to implement your question as another unit test, and run it. |
thanks for the quick response! is this tie resolution specific to your implementation, or do you think the spec outlines this? |
This comes from the PMML spec. I can't pinpoint the exact quote at the moment, but you can find this "theme" repeated over and over when the spec is detailing classification-type models. The JPMML-Evaluator library is very careful about maintaining the insertion order of values when constructing result objects. For example, that's the reason why field |
ok thanks for the info, I will dig to find that! Really appreciate your quick responses 😄 |
Hi @vruusmann,
Looking through the implementation of
multipleModelMethod="max"
for classification, particularly: https://github.com/jpmml/jpmml-evaluator/blob/master/pmml-evaluator/src/main/java/org/jpmml/evaluator/ProbabilityAggregator.java#L207Suppose we have a case with three segments that are predicting three classes and we have the following probabilities:
Then using the max I would expect the average of the first and third model:
max: consider the model(s) that have contributed the chosen probability for the winning category. Return their average probabilities;
The text was updated successfully, but these errors were encountered: