Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/12922#issuecomment-217857785
Ah right, ok. Good point. I was thinking more along the lines of adding
`accuracy` to `BinaryClassificationEvaluator`. I don't think this makes sense
here on a per threshold basis (it's like an "accuracy curve" which I can't say
I've come across before). I'd prefer not to add this as a public API if it's
not a well-used and defined concept. Sorry for the confusion @wangmiao1981
I think we can make the JIRA about adding accuracy to the ml binary
classification evaluator, and that may require the evaluator to compute the
metric itself, not using `BinaryClassificationMetric` (it should be a simple
computation).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
