You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/01/27 14:19:39 UTC
[jira] [Updated] (SPARK-13042) Adding Specificity metric (= true
negative rate) to MulticlassMetrics.scala
[ https://issues.apache.org/jira/browse/SPARK-13042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-13042:
------------------------------
Target Version/s: (was: 1.6.0)
Fix Version/s: (was: 1.6.0)
[~dmarcous@gmail.com] this is also still wrong. It can't target or be fixed in 1.6.0; you shouldn't set these anyway. Please read the guidelines carefully first. I am not clear this is worth adding anyway, and am inclined to close it.
> Adding Specificity metric (= true negative rate) to MulticlassMetrics.scala
> ---------------------------------------------------------------------------
>
> Key: SPARK-13042
> URL: https://issues.apache.org/jira/browse/SPARK-13042
> Project: Spark
> Issue Type: Improvement
> Components: MLlib
> Reporter: Daniel Marcous
> Priority: Minor
> Labels: metrics, mllib
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> Adding Specificity metric (= true negative rate) to MulticlassMetrics.scala
> 1. Add specificity calculations:
> pecificity (SPC) or true negative rate
> SPC = TN / N = TN / (TN+FP)
> False Positive Rate (FPR)
> FPR = FP / N = FP / (FP + TN) = 1-SPC
> SPC = 1 - FPR
> 2. Add specificity tests to :
> mllib/src/test/scala/org/apache/spark/mllib/evaluation/MulticlassMetricsSuite.scala
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org