Talk:Receiver operating characteristic

message: [[[Introduction under-justifying and over-claiming]]]
I don’t like the final two sentences of the intro:
1. “ROC analysis provides tools to select possibly optimal models and to discard suboptimal ones independently from (and prior to specifying) the cost context or the class distribution.”
Guessing at random provides a way of selecting “possibly” optimal models. Why is any ROC-based method preferred? What evidence is there that the ROC-based process leads to superior outcomes?
2. “ROC analysis is related in a direct and natural way to cost/benefit analysis of diagnostic decision making.”
It’s not clear what form this relationship takes, and the subsequent article doesn’t explain it. So it seems like a vague form of over-claiming to me.  — Preceding unsigned comment added by Willbown (talk • contribs) 06:38, 16 July 2023 (UTC)

message: I suggest that the articles "Receiver operating characteristic" and "Detection theory" (Signal detection theory) should be merged.  The merged article should seek a middle path in terms of technical formality and jargon (as simple as possible, but not simpler).  Merged or not, the two articles should be more clearly compatible, if not entirely consistent, since they are basically trying to explain the same underlying thing. Rbfuld (talk) 23:02, 27 January 2008 (UTC)
replies: text: I agree with this; detection theory applies the far more than just radar. Consider SONAR. Detection theory definitley applies to this, however it is certainly not radar. Balluwun-enjoyer (talk) 05:50, 20 May 2023 (UTC)
thread_title:  Merging of articles 

message: For whom was this written? The author displays considerable erudition, but no desire to make his subject palatable to beginners. The second paragraph was enough to choke and die on. I'm not here to be stymied by a pedant - I need to understand ROC curves. I swear - if I ever learn enough about the subject to do so, I will join Wikipedia and rewrite this #$&* entry.64.59.144.85 02:55, 8 February 2007 (UTC)
replies: text: I am in complete agreement with the preceding comment of someone else 13 years earlier!!!  The 4 paragraphs under "Basic Concept" are almost completely unrelated to each other; none of the paragraphs finish what they set out to do, and they are limited to the relatively simple concepts of true and false positives and negatives, essentially making no connection to the nature of an ROC graph.  The figure illustrating the probability of proteasome cleavage isn't even referenced once!  This is still a #$&* entry. Verytas (talk) 00:19, 23 March 2020 (UTC)

text: I second that! I came here to understand what is a better or worse ROC curve, and after having spent 1 hour of reading through the article (and related ones) I still don't have the slightest idea of how to use this for something practical. The lack of human language without tech-jargon is jaw-dropping. Jahibadkaret (talk) 17:01, 25 October 2020 (UTC)
replies: text: This is a common issue with wikipedia math articles. They can be surprisingly jargon-heavy and unfocused. I would recommend a good statistics textbook for learning.  Wqwt (talk) 16:17, 19 October 2023 (UTC)
thread_title:  disappointed 

message: I think that the example plot w/ points A, B, C, C' is misleading or wrong.  C' is intended (I think) to be an example of the effects of inverting the output of the worse-than-random classifier C.  If this is actually what it's meant to represent, the plot is wrong: inverting the output of the classifier doesn't correspond to a mirror reflection across the diagonal, but to a mirroring through the point (0.5,0.5).  (Inverting the test set labels correponds to a mirror reflection across the diagonal.)  I don't have the file used to create the diagram, or I would fix it myself, so I leave this to whoever posted the diagram. 128.62.104.34 22:27, 23 April 2007 (UTC)
replies: text: Hmm, mirroring with the point (0.5, 0.5) is not the same as mirroring with the diagonal line. I believe the example means that the output of worse than random classifier can be simply mirrored with the diagonal line to get point above the diagonal line. In the table you can see that C' is an invert classification of C. Perhaps you can read the source here: . — Indon (reply) — 08:09, 24 April 2007 (UTC)
replies: text: I believe the critique above is correct. Reading your cited source confirms that if you read carefully. Fawcett has the mirroring wrong when he says it is across the diagonal, though his explanation of reversing the decision is correct. that is, true positives become false negatives and vice versa. The contingency table on the wiki page for C' is not an inverted classification of C Because the inversion must occur on the columns in the example and not the rows due to the conjunctive equations. Reversing all decisions would then swap the values in the first row with the values in the second row. Therefore, the mirroring is through the point (0.5,0.5), and a true C' which is a reversed decision of C would be at the point (.12,.76) which is still "better than" pt. A. The explanation after the words about mirroring are what is causing confusion, but it would be useful to inform the reader how the mirroring really takes place. Snthor 15:19, 9 August 2007 (UTC)

text: The lower right triangle corresponds to worse-than-random classifiers, so imho the arrow labels are correct. One might add arrows labeled "higher classification power" pointing away from the diagonal. I agree that the presented contingency table for C' is incorrect, instead of interchanging the columns one has to interchange the rows, since the row index represents the suggested classification. When calculating the TPR and FPR for the modified matrix, one finds that TPR changes to 1-TPR and FPR changes to 1-FPR, so also the presented numbers below the matrix are wrong, as well as the position of C' in the plot. The replacement of (x,y) by (1-x,1-y) corresponds to a mirroring at (0.5, 0.5). Kero6581 (talk) 08:12, 6 May 2009 (UTC)
replies: text: ok, I corrected the text so that the squares are now correct. The only thing left is to correct the diagram such that the point C' is at (.12,.76). I hope Indon still has his original file, that would make it much easier to correct the figure. Greetings --hroest 12:08, 10 July 2009 (UTC)
replies: text: Ok, new figure done. Contact me if modifications are necessary. Kai walz (talk) 20:57, 8 November 2009 (UTC)
thread_title:  ROC example misleading or wrong 

message: The notation used in the figure ("How a ROC curve can be interpreted") in the fourth section ("Further interpretations") is inconsistent with the notation introduced in the first two sections ("Basic concept" and "ROC Space").  The figure uses TP, FP, TN and FN instead of TPR, FPR, TNR and FNR.  Aside from being confusing, it is actually misleading since TP, FP, etc. were already introduced in the earlier sections as having different meanings than TPR, FPR, etc.  What is more, the figure's notation isn't even internally consistent.  The axis labels on the ROC graph should be "TP" and "FP", not "P(TP)" and "P(FP)".  Alternatively, to show explicit dependence of the true positive rate and false positive rate on the threshold value, the axis labels could be "TP(θ)" and "FP(θ)", where the threshold value θ needs then to be introduced in the graph of the probability density curves for the detection statistic.  And while I'm picking nits, why aren't the axes of the probability density graph labelled, and for that matter, why don't any of the three subfigures in this image have titles?
Don't get me wrong, I don't want to get rid of this image.  For me it is the one illustration that allowed me to "get" what the ROC curve actually quantifies.  Which is why I think it is important that it be brought into conformance with the rest of the article.  I can see from the article's history that the image itself predates the discussion in the "Basic concept" and "ROC space" sections, so I imagine that the original creator of the image (Kku?) might be resistant to having it replaced with an updated version.  However, our collective goal is for the overall article to be as clear as possible, and the best way that I can see to do that is to maintain the notation of the "Basic concept" section and to update the figure accordingly.
Here are the changes that I would propose to the figure:
 - Titles for each of the three subfigures (these could be placed in the figure caption as long 
   as the subfigures are labelled with a), b) and c))
 - Axis labels where appropriate
 - Replace TP, FP, etc. with TPR, FPR, etc.
 - Introduce θ as the threshold value and replace P(TP) and P(FP) with TPR(θ) and FPR(θ)
One other thing worth mentioning on the topic of consistency, is that the confusion matrix in the figure is of a different form than that introduced in the "Basic concept" section, having its columns sum to 1 rather than to the respective probabilities of the underlying event occurring or not.  I don't think that this should be changed in the name of consistency, however, because as it is, it provides a direct link between the two other subfigures in the image.  If the confusion matrix were altered so that the columns sum respectively to P and N, then this link would be lost and the subfigure would only serve to introduce (dare I say it?) confusion.
Personally, if effort will be taken to update this figure, I think it might be wortwhile to introduce one more subfigure at the top showing the information flow (underlying two-state process --> observable data --> detection statistic --> decision), but this may not be the best choice of language if my stated goal is to enforce consistency with the rest of the article.
JanRu 20:26, 26 April 2007 (UTC)
thread_title:  Inconsistent Notation 

message: In the section, "ROC Space", the info-box is referenced as containing evaluation metrics. Perhaps inadvertently, the word metric is hyperlinked to the wiki page on metrics, as in metric space distances. The reader may be inclined to believe from this that the info-box contains metrics. This is not the case. None of the "evaluation" metrics listed are true metrics in the mathematical sense. I would recommend deleting the hyperlink.
:I agree, I removed that link Bayle Shanks (talk) 22:12, 6 November 2009 (UTC)
thread_title:  ROC space and metrics 

message: The article says about d' "... under the assumption that both these distributions are normal with the SAME standard deviation" (my emphasis). But the article about d' uses "the standard deviation of the noise distribution". Stevemiller 04:46, 10 October 2007 (UTC)
thread_title:  d' (d-prime) 

message: Does the number of observations affect the ROC curve at all?  With only one observation isn't it possible to have 100% sensitivity (no false negatives) and 100% specificity (no false positives)?  Presumably I'm missing something because if that's the case having a good point on a ROC curve doesn't guarantee a good classifier.  pgr94 (talk) 18:55, 24 January 2009 (UTC)
thread_title:  Number of observations - irrelevant? 

message: This is an excellent addition to this article - very helpful for people wanting to dive deeper. Thanks so much. 128.220.160.6 (talk) 00:48, 9 March 2009 (UTC)
replies: text: Perhaps we should move this table into either the Confusion matrix or Binary classification article. As of right now, various concepts such as sensitivity and specificity, positive and negative predictive value, and accuracy each have their own articles, each repeating the same information about the various relationships between true positives and false positives. Perhaps we should consolidate some of this information into a more comprehensive article on a more general/introductory page. Many of these basic definitions (specificity, selectivity, positive/negative predictive value) are useful basic information and right now the only place to find a handy table is in the Receiver operating characteristic page, which is a little too obscure/advanced to warrant being the main location for this information. The sensitivity and specificity page has already started to become a more general page: unlike positive and negative predictive value which have separate articles, sensitivity and specificity has attempted to introduce much of this terminology together. For now I have added this table to the sensitivity and specificity article. 171.64.15.56 (talk) 17:51, 30 October 2009 (UTC)

text: I assume "eqv." means "equivalent" 171.64.15.56 (talk) 17:44, 30 October 2009 (UTC)
thread_title: Terminology and derivations from a confusion matrix

message: From Revision #314192656 by 151.148.122.100 "Failed to parse (unknown function\MCC): \MCC = (TPTN - FPFN)/ \sqrt{P N P' N'}" ... reverted to working formula, however, the formula is rendered as a PNG - anyone who knows how to enforce text rendering, please be my guest. - Dlefree-loc-work (talk) 08:55, 21 September 2009 (UTC)
thread_title: Math Parser Error

message: Perhaps something should be added to note that the further you move towards the upper-right in the ROC graph, the more often that the classifier gives you a positive answer. So, I think that movement in a diagonal direction towards the upper right corresponds to biasing the classifier to return a positive answer more often, without improving its accuracy. I'd add this myself, but I'd like someone more knowledgable to double-check it first. Bayle Shanks (talk) 22:07, 6 November 2009 (UTC)
replies: text: The holy grail is the upper left, not the upper right.  You are correct about the upper right.  It's always easy to get the upper right: Just label every point as a "yes".  (Or lower left, for "no".)  All ROCs pass through those two points.  If you think the average reader would benefit, and you would like to add a few words to that effect, do it! Jmacwiki (talk) 15:07, 10 July 2011 (UTC)
thread_title:  Positiveness 

message: ROC curve is also called a "lift curve" according to the book "Mastering Data Mining" by Berry and Linoff.  —Preceding unsigned comment added by AndrewHZ (talk • contribs) 03:48, 6 December 2009 (UTC)
replies: text: Yes, in data mining the same approach is used to indicate the impact of using a predictive model in a real world marketing environment.  It is known as a lift curve or a gains curve, and somewhat less often as an ROC curve.  Duncan (talk) 15:16, 10 December 2009 (UTC)
thread_title:  "Lift Curve" 

message: Just gone looking for a source for the following summary statistic:
# the area between the ROC curve and the no-discrimination line
If you've got a reference for this one, it'd be much appreciated.  —Preceding unsigned comment added by Noogz (talk • contribs) 06:23, 8 March 2010 (UTC)
replies: text: If I understand the question, this is the same as the Gini coefficient, which is already referenced in the article.  (Or maybe 1-Gini, I don't recall.) Jmacwiki (talk) 15:09, 10 July 2011 (UTC)
thread_title:  Discrimination summary statistic 

message: How about discussing the meaning and use of cut offs as illustrated here? (The cut offs are the labels 0.1, 0.2, etc on the curve.) AndrewHZ (talk) 16:55, 6 December 2010 (UTC)
thread_title:  Cut offs 

message: The false positive rate is the conditional probability that a person truly has a disease given that they test positive. In other words, P(D|+). In signal detection theory there is something called the false alarm rate, which is being incorrectly used in this article as the false positive rate. This is all made clear in Statistical Methods For Rates And Proportions by David L. Fleiss. 
This misunderstanding of the false positive rate is unfortunately fairly widespread, and having it misstated in this article is no help.  —Preceding unsigned comment added by 12.190.115.98 (talk) 14:06, 24 January 2011 (UTC)
replies: text: No, the the conditional probability that a person truly has a disease given that they test positive is the positive predictive value. The false positive rate is the conditional probability that a person tests positive given that they don't have the disease. --Qwfp (talk) 14:36, 24 January 2011 (UTC)
replies: text: Quite so.  And the latter is identical to the false alarm rate.  (The names really aren't opaque.  They mean what they say, and they say equivalent things!) Jmacwiki (talk) 07:04, 2 February 2013 (UTC)
thread_title:  incorrect definition of false positive rate 

message: Is there a ref for this  thanks. Zulu Papa 5 * (talk) 02:10, 7 March 2011 (UTC)
thread_title:  ref 

message: Just noted that the Confusion matrix page gives the columns as predicted values and rows as actual values, whereas the confusing matrix used on this page has swapped the meaning of columns and rows.  —Preceding unsigned comment added by 80.216.132.209 (talk) 20:49, 10 April 2011 (UTC)
thread_title:  Confusing matrix 

message: Mistakes in:
:A completely random guess would give a point along a diagonal line (the so-called line of no-discrimination) from the left bottom to the top right corners (regardless of the positive and negative base rates). An intuitive example of random guessing is a decision by flipping coins (heads or tails).
This should be a biased coin. And more is not good. — Preceding unsigned comment added by 129.125.21.37 (talk) 10:34, 16 April 2012 (UTC)
thread_title:  Mistakes 

message: In the section "Other measures": The graph shows that if one detects at least 60% of the epitopes in a virus protein, at least 30% of the output is falsely marked as epitopes. I wonder if the second half of the sentence is wrong -- we should say "at least 30% of non-epitopes are falsely detected". MaigoAkisame (talk) 19:41, 8 August 2012 (UTC)
thread_title:  Misinterpretation of epitope detection result? 

message: Can someone add some comments/references on the choice of the threshold?
Indeed, after measuring the ROC curve of a system, one may want to optimize the system by choosing a specific point on the curve, i.e. a specific threshold, either by:
* minimizing the distance with the upper-left corner
* maximizing the distance with the random line (orthogonal projection)
* staying below a given FPR or above a given TPR (to comply with project goals)
Lagaffe (talk) 10:42, 12 November 2012 (UTC)
thread_title:  Threshold choice 

message: The AUC section contains a formula with undefined variables, viz., X, Y and k. This is not acceptable in an article. I presume it was just copied from some text somewhere in which the definitions were given. If the author of that section is monitoring this talk page, I implore him/her to please define the variables. This is a bad (and annoying) practice and we should try to force clear definitions in every instance on wikipedia. Formulas are nearly useless without the definitions of their elements. Chafe66 (talk) 22:21, 30 January 2013 (UTC)
thread_title:  Undefined Variables in Formula 

message: In the paragraph headed "Z-transformation", I think the blue link on the first occurrence of the phrase "Z-transformation" is in error.  The linked page seems to have nothing to do with the transformation being referred to here.  The reference should be to some transformation associated with the Normal distribution.  Stephen Robertson (talk) 09:42, 24 April 2013 (UTC)
thread_title:  Bad link for Z-transformation? 

message: The Basic concept section (which begins "A classification model (classifier or diagnosis) is...") contains a piece of text identical to text I've found in page 3 of this document.  That document has a publishing date of 2003, while the text here seems to have been added in 2007 by this edit.  As a side note, while I initially thought the paragraphs following it were also a copyvio, they have in fact apparently been reproduced in this book published in 2010.  AdventurousSquirrel (talk) 13:09, 13 January 2014 (UTC)
thread_title:  Possible copyvio 

message: This article has been tagged for external link cleanup since March 2010. In looking over the existing external links, most of them are very borderline; they're mostly to personal pages of mathematicians working in the field or mathematicians' collections of academic papers on the subject. I can see an argument for each one to be included, but taken as a whole, they do feel kind of crufty and excessive.
I fully expect for at least part of this particular removal to be (justifiably) overridden by the regular editors -- I'm working through cleanup backlog of the external-link-template categories; I'm not a regular here -- because unlike the more egregious instances of "holy 73 links to personal webpages, Batman!" that the external-link-template tends to collect, I'm really on the fence about this one. I decided, however, to remove the external links section entirely, toss them here onto the talk page, and ask that instead of y'all reverting my edit wholesale that you instead take the chance to consider each link carefully and manually add back only the most justified and useful links to the article.
For what it's worth, and as an external opinion, the ones I really was this close to retaining were Kelly Zou's bibliography and the web-based calculator by John Eng.
* Kelly H. Zou's bibliography of ROC literature and articles
* Tom Fawcett's ROC Convex Hull: tutorial, program and papers
* Peter Flach's tutorial on ROC analysis in machine learning
* The magnificent ROC – An explanation and interactive demonstration of the connection of ROCs to archetypal bi-normal test result plots
* Web-based calculator for ROC Curves – by John Eng
* Convex Hull, cost trade off, etc
--rahaeli (talk) 15:46, 18 May 2014 (UTC)
thread_title:  External links  

message: Just curious how the hell the name came about, as it seems a bit flaunty given that it's just true positives vs false positives.  — Preceding unsigned comment added by Mmkstarr (talk • contribs) 00:56, 18 March 2016 (UTC)
thread_title:  Etymology of "receiver operating characteristic"? 

message: The article here holds a relatively critical view of AUC for estimating classifier performance based on the paper by Hand. This research seems to be mostly superseded by the more recent paper by Flach cited later.
"Small-sample precision of ROC-related estimates" explicitly talks about small sample estimates, which is not relevant for machine learning applications.
Therefore paragraph seems inconsistent to me. There seems to be no current literature suggesting that AUC actually is not a good measure.
Still the article goes on saying "One recent explanation of the problem with ROC AUC " which implies that there is a problem. Andreas Mueller (talk) 20:47, 29 April 2016 (UTC)
thread_title:  Criticism of AUC debunked in recent research. 

message: Hi,
I am new to Wikipedia, so please pardon me if this is not the correct space for this.
I would like to add information about the Total Operating Characteristic (TOC) curve. This is an alternative to the ROC curve that still provides all of the information the ROC curve presents such as area under the curve.  However, it is designed slightly different so that you would be able to recreate a confusion matrix showing the hits, misses, correct rejections, and false alarms for each threshold. Dr. Robert Gil Pontius came up with the TOC curve as an improvement to the ROC curve, and he has a paper published in the International Journal of Geographical Information Science called, “The total operating characteristic to measure diagnostic ability for multiple thresholds” which explains how to construct a TOC curve and the advantages of using it over the ROC.
Should the TOC be added to the ROC article, or should it have its own article? Because we have a lot of content on the TOC curve, I think we should try to make a separate page for TOC. However, based on the little information I know about Wiki, creating a page and getting it approved is a more difficult task?
Thank you!
 Crobbins5 (talk) 06:55, 19 March 2018 (UTC)
thread_title:  Total operating characteristic (TOC) curve as alternative to ROC 

message: I just created an ROC image which might be interesting for this article:
--MartinThoma (talk) 19:53, 24 June 2018 (UTC)
replies: text: Excellent, exactly what this article is missing. (See my comment under the dissapointed section, above) Please add this! Jahibadkaret (talk) 17:04, 25 October 2020 (UTC)
thread_title:  Image 

message: Most ROC examples show a curve in a step-wise form, i.e., at a given cutoff value either TPR or FPR change, leading to a curve that is comprised of horizontal and vertical lines which are then only "smoothed" by the number of points. If at a given cutoff value, though, both, a TRUE and and FALSE data point are classifed as positive, because for some reason they have the same predicted value, the curve should provide a diagonal line piece as I understand (and as it is implemented, e.g., in the R package ROCR). I have seen versions, though, where in this case the curve is rather created by still using horizontal and vertical line pieces, usually in a manner that a fictive cutoff point is created as if by an infinite small amount the FALSE observation is classified as positive before the TRUE observation is classified. Obviously, this will reduce the AUC in comparison to the straight (diagonal) line.
Is there a "correct" approach to this?
Jenskauf (talk) 14:19, 24 May 2020 (UTC)
thread_title:  Correct curve when TPR and FPR both change at a cutoff value? 

message: and  Is there a reason to have the ROC graph in a hand-drawn style? I can redraw the graph in a more conventional style if it fits the tone of the article better. Cheers, cmɢʟee⎆τaʟκ 16:04, 13 August 2021 (UTC)
replies: text: that would be great! –CWenger (^ • @) 16:15, 13 August 2021 (UTC)
replies: text: I simply like that style :-) If you create a new one, please reference this one and upload it as a new file --MartinThoma (talk) 17:36, 19 August 2021 (UTC)
replies: text:  I like it too, just doesn't seem appropriate for an encyclopedia. –CWenger (^ • @) 17:49, 19 August 2021 (UTC)
replies: text:  Why do you think so? --MartinThoma (talk) 16:25, 22 August 2021 (UTC)
replies: text: The pseudo-hand-drawn squiggly lines and Comic Sansesque font give it an informal look more appropriate for a blog post than an encyclopedia article. 19:50, 22 August 2021 (UTC)
replies: text:  Thanks,  cmɢʟee⎆τaʟκ 20:36, 5 September 2021 (UTC)
replies: text:  Looks great, thanks! –CWenger (^ • @) 21:38, 5 September 2021 (UTC)

text: Hi, I opened an account just for this. I made some gif animations a while ago that vividly show how the graph is extracted and I hope they can be used here. Not sure how to share them here, so I would appreciate help. Iliumm (talk) 10:10, 24 April 2023 (UTC)
thread_title:  xkcd-style graph 

message: Would anyone object if I simply booted this entire paragraph out of the lead section?
The ROC curve is created by plotting the true positive rate (TPR) against the false positive rate (FPR) at various threshold settings. The true-positive rate is also known as sensitivity, recall or probability of detection in machine learning. The false-positive rate is also known as probability of false alarm and can be calculated as (1 − specificity). It can also be thought of as a plot of the power as a function of the Type I Error of the decision rule (when the performance is calculated from just a sample of the population, it can be thought of as estimators of these quantities). The ROC curve is thus the sensitivity or recall as a function of fall-out. In general, if the probability distributions for both detection and false alarm are known, the ROC curve can be generated by plotting the cumulative distribution function (area under the probability distribution from  to the discrimination threshold) of the detection probability in the y-axis versus the cumulative distribution function of the false-alarm probability on the x-axis.
As the second paragraph in the entire article, it's really a bit much, a perfect example of the complaints about readability that have been expressed here numerous times over the years. Why are we being given detailed instructions on how to create and interpret a ROC curve, when we've barely been told what that even is or why we'd want to?
With the nightmare above excised, the entire lead then becomes this:
A receiver operating characteristic curve, or ROC curve, is a graphical plot that illustrates the diagnostic ability of a binary classifier system as its discrimination threshold is varied. The method was originally developed for operators of military radar receivers starting in 1941, which led to its name.
ROC analysis provides tools to select possibly optimal models and to discard suboptimal ones independently from (and prior to specifying) the cost context or the class distribution. ROC analysis is related in a direct and natural way to cost/benefit analysis of diagnostic decision making.
The ROC curve was first developed by electrical engineers and radar engineers during World War II for detecting enemy objects in battlefields and was soon introduced to psychology to account for perceptual detection of stimuli. ROC analysis since then has been used in medicine, radiology, biometrics, forecasting of natural hazards, meteorology, model performance assessment, and other areas for many decades and is increasingly used in machine learning and data mining research.
The ROC is also known as a relative operating characteristic curve, because it is a comparison of two operating characteristics (TPR and FPR) as the criterion changes.
To summarize: If used correctly, ROC curves are a very powerful tool as a statistical performance measure in detection/classification theory and hypothesis testing, since they allow having all relevant quantities in one plot.
Which, you know, is actually reasonable. It needs some minor cleanup to address the redundancy in the first  and third paragraphs, now glaringly apparent without all that faff between them. And that "to summarize" simply has to go. (It's a lead section, duh! Its entire job is to summarize.) But, some rough edges notwithstanding, it's at least a passable attempt at introducing the concept of a ROC curve to the reader.
If we don't boot the Paragraph From Hell, then I'd like to at least trim it way, waaaay down. Like, literally a single sentence. Perhaps:
The ROC curve for a given decision model plots the rate of true positive results vs. false positive results at various threshold settings, providing a means of evaluating the model's performance.
Oversimplified? Hell yes. But that's the point of a lead section, and the reason there's an entire article right below it that fills in the details. (As long as it's merely oversimplified, and not wrong. I don't claim to be a topic expert; heck I'm not even particularly familiar with the topic.) -- (please use  on reply) FeRDNYC (talk) 16:42, 20 October 2021 (UTC)
replies: text: There should be a list of Wikipedia red-flags (probably is, somewhere), and that should definitely be on it. If you have to summarize your lead section, something's not right up there. -- FeRDNYC (talk) 16:52, 20 October 2021 (UTC)
thread_title:  Lead reduction 

message: Fellow Wikipedians: I've proposed some changes to the formula infobox transcluded into this article, with the goal of trimming down its overpowering (if not excessive) width. My original message with some explanatory notes is at Template talk:Confusion matrix terms#Template_width, and you can see the revised template layout I've proposed by viewing its sandbox version.
There have been no responses over there in well over two months, and since the changes I'm proposing are significant enough to possibly be contentious, I wanted to invite any interested Wikipedians to discuss them over at the template's talk page. Thanks! FeRDNYC (talk) 00:12, 5 January 2022 (UTC)
thread_title:  Proposed changes to transcluded formula template