Skip to main content

How do you interpret High precision

Precision measures how many of the positively predicted instances by a model are actually true positive instances. It quantifies the accuracy of positive predictions made by the model.

Mathematically, precision is defined as:

Precision=True PositivesTrue Positives+False Positives

Where:

  • True Positives (TP) are the number of correctly predicted positive instances.
  • False Positives (FP) are the number of incorrectly predicted positive instances.

Precision ranges between 0 and 1, with higher values indicating a higher proportion of true positive predictions among all positive predictions.


  • When precision is high, it means that a model is making positive predictions very selectively, and when it predicts a positive instance, it's usually correct. In other words, the model is cautious about making positive predictions.
  • High precision and a high false-negative rate are often related. 
  • When a model is designed to have very high precision, it tends to be cautious about making positive predictions. 

  • This caution can lead to a situation where the model avoids making many false-positive errors but, in doing so, ends up missing some true positive instances. These missed true positives contribute to a high false-negative rate.

False Negative Rate:

  • The false negative rate measures the proportion of actual positive instances that were incorrectly predicted as negative by the model. It quantifies how many positive instances the model missed.

Mathematically, the false negative rate is defined as:

False Negative Rate=False NegativesFalse Negatives+True Positives

Where:

  • False Negatives (FN) are the number of actual positive instances that were incorrectly predicted as negative.

A high false negative rate means that the model is missing a significant number of actual positive instances. It indicates that the model is not very sensitive to positive instances; it's letting many of them go undetected.


Labels:

Comments

Post a Comment

Popular posts from this blog

What is the difference between Elastic and Enterprise Redis w.r.t "Hybrid Query" capabilities

  We'll explore scenarios involving nested queries, aggregations, custom scoring, and hybrid queries that combine multiple search criteria. 1. Nested Queries ElasticSearch Example: ElasticSearch supports nested documents, which allows for querying on nested fields with complex conditions. Query: Find products where the product has a review with a rating of 5 and the review text contains "excellent". { "query": { "nested": { "path": "reviews", "query": { "bool": { "must": [ { "match": { "reviews.rating": 5 } }, { "match": { "reviews.text": "excellent" } } ] } } } } } Redis Limitation: Redis does not support nested documents natively. While you can store nested structures in JSON documents using the RedisJSON module, querying these nested structures with complex condi...
Post a Comment
Read more

Error: could not find function "read.xlsx" while reading .xlsx file in R

Got this during the execution of following command in R > dat Error: could not find function "read.xlsx" Tried following command > install.packages("xlsx", dependencies = TRUE) Installing package into ‘C:/Users/amajumde/Documents/R/win-library/3.2’ (as ‘lib’ is unspecified) also installing the dependencies ‘rJava’, ‘xlsxjars’ trying URL 'https://cran.rstudio.com/bin/windows/contrib/3.2/rJava_0.9-8.zip' Content type 'application/zip' length 766972 bytes (748 KB) downloaded 748 KB trying URL 'https://cran.rstudio.com/bin/windows/contrib/3.2/xlsxjars_0.6.1.zip' Content type 'application/zip' length 9485170 bytes (9.0 MB) downloaded 9.0 MB trying URL 'https://cran.rstudio.com/bin/windows/contrib/3.2/xlsx_0.5.7.zip' Content type 'application/zip' length 400968 bytes (391 KB) downloaded 391 KB package ‘rJava’ successfully unpacked and MD5 sums checked package ‘xlsxjars’ successfully unpacked ...
Post a Comment
Read more

Training LLM model requires more GPU RAM than storing same LLM

Storing an LLM model and training the same model both require memory, but the memory requirements for training are typically higher than just storing the model. Let's dive into the details: Memory Requirement for Storing the Model: When you store an LLM model, you need to save the weights of the model parameters. Each parameter is typically represented by a 32-bit float (4 bytes). The memory requirement for storing the model weights is calculated by multiplying the number of parameters by 4 bytes. For example, if you have a model with 1 billion parameters, the memory requirement for storing the model weights alone would be 4 GB (4 bytes * 1 billion parameters). Memory Requirement for Training: During the training process, additional components use GPU memory in addition to the model weights. These components include optimizer states, gradients, activations, and temporary variables needed by the training process. These components can require additional memory beyond just storing th...
Post a Comment
Read more