In the last year of my bachelor’s degree, I learned an interesting fact during a customs class:
If a person appears suspicious, they detain him and deliberately prolong the interrogation process. He was asked very simple but annoying questions. Here one person asks a question, and another employee stands a short distance away and observes as if he was doing something else. If a person is really carrying a prohibited, harmful, or dangerous item across the border, selling, or importing it, they become overly irritable and overly emotional. Such a person is already considered quite suspicious.
That is, the probability of P (Person = Criminal / Reaction = Emotional) is high. However, this does not mean that all emotional individuals are criminals; If some people are suspicious, it may simply be due to their neurotic or other health problems, current mood, or first trip.
There is a saying, “Where there is no fire, there is no smoke.” That is, if I see smoke, then there is a fire. I wonder how right I am in this opinion?
Let’s say I’m making a fire detector. Thus, this detector should detect fire cases as accurately as possible and not cause a disturbance by giving a false fire signal. That is, the detector should not endanger me or disturb me unnecessarily.
Here, a fire that the detector can give a true warning to is a “True Positive” result. There is a fire (the event is positive) and the detector has identified it correctly (the result is true).
In the absence of fire, the alarm is “False Positive”. There is no fire, but the detector gives a positive signal by mistake. Let me note that this does not mean that the positive is good, but that the affirmation of the incident that took place.
The fact that the detector does not signal in the absence of fire is “True Negative”. No incident occurred and the detector did not signal according to the situation.
Failure to signal in case of fire (this is the most dangerous situation) is “False Negative”. An accident occurs, but the detector can not see it.
Type 1 is believing that something is not wrong, and Type 2 is not believing that something exists (it is not the same as believing that it does not exist).
In Type 1 error we reject the true Null Hypothesis, but in Type 2 error we fail to reject the false Null Hypothesis (we cannot accept Null Hypothesis, we can only fail to reject it due to insufficient data, time interval, or other impediments).
Generally, Type 1 error is considered more dangerous, because we continue to believe in something that does not exist, and we do not re-investigate. The investigation continues until it finds a Type 2 error. However, this comparison varies from situation to situation. Fire, health problems, accidents, etc. Type 1 error is often more reliable in matters related to human life because even if I am worried by mistake, I will insure myself (call the fire brigade, take vitamins, stay at home, etc.) and the second type of mistake will give me peace of mind and I will be caught unprepared. Otherwise, even if the detector gives the wrong signal, I will search everywhere until I find the problem. As a result, I will not face life-threatening.
To make such a detector, I have to program it (in the language of Data Science, train it), and finally, test it.
Here, our model transforms the prior probability into a posterior with the data we give it. That is before there was historical data of fire cases the probability of fire cases was 50%. Now it has the data to learn. Based on this data, a new result is obtained according to Bayes’ theorem (P (Probability of occurrence of the event | If data is given)). During the test, we construct a matrix similar to the one above. And there we record the number of TP, TN, FP, FN cases. These numbers show how accurate our model is. Such a matrix is called a confusion matrix.
Let’s say our model detects 80% of fires. At first glance, the result is not bad. But when we look at the sentence again, we see that I only find 80% of fire cases. What about when there is no fire? Maybe our detector will activate such an alarm more often in the absence of fire and cause additional inconvenience?
Here, 80% is called the “sensitivity rate”. That is, our model is 80% sensitive to fires and detects 80% of fires. This is only for fires. Taking this as the core value of our model leads to a “base rate fallacy”.
“Base rate” – the percentage of fires that occur (the ratio of the number of fires to the total time, for example, once in 5 years.
We also need to know the “specificity rate”. The degree of specificity is the correct detection of non-fire cases by the detector, ie how accurate the detector can find when there is no fire.
We use the following ratios to evaluate the model correctly.
In the Confusion Matrix, the TP / (TP + FP) ratio is called precision. That is the ratio of the number of times the signal is activated during a fire to the total time the signal is activated (what percentage of alarm cases occur at the right time).
The TP / (TP + FN) ratio is called recall. That is the ratio of the number of fires in which the signal is activated to all fires (what percentage of alarms are activated during a fire). Recall and sensitivity are the same concepts.
Besides, there is an accuracy rate. It is also equal to the ratio (TP + TN) / (TP + FP + TN + FN). That is the ratio of the times when all the alarms work properly (activated in case of fire, not activated in case of fire) to all cases (note that for highly imbalanced data we rely on F1 score rather than accuracy rate).
These 3 ratios are very important to evaluate the model. It should also be noted that, in fact, relative values are more important than absolute values for any assessment. For example, the absolute grade you get from the exam (say, 85 points) is insignificant when we do not know the maximum score. But when it comes to 85/100, this price is significant. The evaluation of the model is based on the same simple logic.
I hope that in this blog your discussion of the Bayesian theorem has expanded a bit.
Source for image: https://challengersdeep.wixsite.com/website/post/od-olmayan-yerdən-tüstü-çıxmaz
Confusion Matrix Is No More A Confusion for Dat...
Confusion Matrix: Detailed intuition and trick ...
When the Measurement’s Accuracy Misleads�...
How to Choose Evaluation Metrics for Classifica...
How Machine Learning Models Fail to Deliver in ...
Decluttering the performance measures of classi...
Metrics to Evaluate your Classification Model t...
Accuracy and its shortcomings: Precision, Recal...
Evaluation Metrics With Python Codes
Evaluating A Classification Model for Data Science
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s