惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News and Events Feed by Topic
V
V2EX
博客园 - 【当耐特】
Vercel News
Vercel News
雷峰网
雷峰网
爱范儿
爱范儿
WordPress大学
WordPress大学
云风的 BLOG
云风的 BLOG
S
Securelist
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Microsoft Azure Blog
Microsoft Azure Blog
F
Full Disclosure
有赞技术团队
有赞技术团队
Hugging Face - Blog
Hugging Face - Blog
NISL@THU
NISL@THU
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Attack and Defense Labs
Attack and Defense Labs
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
Microsoft Security Blog
Microsoft Security Blog
腾讯CDC
P
Proofpoint News Feed
B
Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
K
Kaspersky official blog
I
InfoQ
Google Online Security Blog
Google Online Security Blog
L
LINUX DO - 最新话题
Project Zero
Project Zero
Engineering at Meta
Engineering at Meta
V
Visual Studio Blog
AI
AI
Schneier on Security
Schneier on Security
B
Blog RSS Feed
T
Tor Project blog
H
Help Net Security
H
Hackread – Cybersecurity News, Data Breaches, AI and More
L
LINUX DO - 热门话题
阮一峰的网络日志
阮一峰的网络日志
S
Security @ Cisco Blogs
T
Threat Research - Cisco Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
C
Cyber Attacks, Cyber Crime and Cyber Security
G
Google Developers Blog
Google DeepMind News
Google DeepMind News
V2EX - 技术
V2EX - 技术
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
A
Arctic Wolf
Webroot Blog
Webroot Blog
Recent Commits to openclaw:main
Recent Commits to openclaw:main

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
56 Logistic Regression: Classification With a Probability
Akhilesh · 2026-05-07 · via DEV Community

You want to predict yes or no. Spam or not spam. Sick or healthy. Fraud or legit.

That's a classification problem. And despite its confusing name, logistic regression is one of the best tools for it.

It doesn't predict a number. It predicts a probability. Then it uses that probability to make a yes or no decision.

Simple idea. Powerful in practice.


What You'll Learn Here

  • Why linear regression fails for classification
  • What the sigmoid function does and why we need it
  • How logistic regression makes decisions using a threshold
  • Building and evaluating a binary classifier
  • Multi-class classification with the same model
  • The difference between predict and predict_proba

Why Not Just Use Linear Regression?

You might think: house prices were numbers, exam scores were numbers, so just use linear regression and predict 0 or 1.

The problem is linear regression can predict values outside 0 and 1. It might predict 1.8 or -0.3. Those don't make sense as probabilities.

Also, a straight line is a bad fit for binary data. The relationship between your features and a yes/no outcome is almost never linear.

You need something that:

  • Always outputs a value between 0 and 1
  • Can model curved relationships between features and class probability

That's where the sigmoid function comes in.


The Sigmoid Function

The sigmoid function takes any number and squashes it to a value between 0 and 1.

sigmoid(z) = 1 / (1 + e^(-z))

Enter fullscreen mode Exit fullscreen mode

When z is very large, sigmoid(z) is close to 1.
When z is very small (very negative), sigmoid(z) is close to 0.
When z is 0, sigmoid(z) is exactly 0.5.

That S-shaped curve is why it works for probability.

import numpy as np
import matplotlib.pyplot as plt

def sigmoid(z):
    return 1 / (1 + np.exp(-z))

z = np.linspace(-10, 10, 300)
prob = sigmoid(z)

plt.figure(figsize=(8, 4))
plt.plot(z, prob, color='blue', linewidth=2)
plt.axhline(y=0.5, color='red', linestyle='--', alpha=0.7, label='Threshold = 0.5')
plt.axvline(x=0, color='gray', linestyle='--', alpha=0.5)
plt.xlabel('z (raw score)')
plt.ylabel('Probability')
plt.title('Sigmoid Function')
plt.legend()
plt.grid(True, alpha=0.3)
plt.savefig('sigmoid.png', dpi=100)
plt.show()

# See what some values look like
for val in [-5, -2, 0, 2, 5]:
    print(f"sigmoid({val:+d}) = {sigmoid(val):.3f}")

Enter fullscreen mode Exit fullscreen mode

Output:

sigmoid(-5) = 0.007
sigmoid(-2) = 0.119
sigmoid( 0) = 0.500
sigmoid(+2) = 0.881
sigmoid(+5) = 0.993

Enter fullscreen mode Exit fullscreen mode

So logistic regression does this:

  1. Computes a raw score z = w1*x1 + w2*x2 + ... + b (same as linear regression)
  2. Passes z through sigmoid to get a probability between 0 and 1
  3. If probability >= 0.5, predict class 1. If < 0.5, predict class 0.

That's the whole model.


Your First Logistic Regression Classifier

from sklearn.datasets import load_breast_cancer
from sklearn.linear_model import LogisticRegression
from sklearn.model_selection import train_test_split
from sklearn.preprocessing import StandardScaler
from sklearn.metrics import accuracy_score, classification_report
import pandas as pd

# Load data - predict if tumor is malignant or benign
data = load_breast_cancer()
X = pd.DataFrame(data.data, columns=data.feature_names)
y = data.target  # 0 = malignant, 1 = benign

print(f"Features: {X.shape[1]}")
print(f"Samples:  {X.shape[0]}")
print(f"Class distribution: {pd.Series(y).value_counts().to_dict()}")

Enter fullscreen mode Exit fullscreen mode

Output:

Features: 30
Samples:  569
Class distribution: {1: 357, 0: 212}

Enter fullscreen mode Exit fullscreen mode

# Split and scale
X_train, X_test, y_train, y_test = train_test_split(
    X, y, test_size=0.2, random_state=42, stratify=y
)

scaler = StandardScaler()
X_train_s = scaler.fit_transform(X_train)
X_test_s  = scaler.transform(X_test)

# Train
model = LogisticRegression(random_state=42, max_iter=1000)
model.fit(X_train_s, y_train)

# Predict
y_pred = model.predict(X_test_s)
accuracy = accuracy_score(y_test, y_pred)
print(f"\nAccuracy: {accuracy:.3f}")

Enter fullscreen mode Exit fullscreen mode

Output:

Accuracy: 0.974

Enter fullscreen mode Exit fullscreen mode

97.4% accuracy on a cancer detection problem. Not bad at all.


predict vs predict_proba

This is something a lot of beginners miss.

model.predict() gives you the final class label: 0 or 1.
model.predict_proba() gives you the actual probability for each class.

The probability is often more useful than the hard label.

# Look at raw probabilities vs final predictions
proba = model.predict_proba(X_test_s)

print(f"{'Sample':<8} {'P(malignant)':<15} {'P(benign)':<12} {'Predicted':<12} {'Actual'}")
print("-" * 60)

for i in range(8):
    print(f"{i:<8} {proba[i][0]:.3f}          {proba[i][1]:.3f}        "
          f"{data.target_names[y_pred[i]]:<12} {data.target_names[y_test[i]]}")

Enter fullscreen mode Exit fullscreen mode

Output:

Sample   P(malignant)    P(benign)    Predicted    Actual
------------------------------------------------------------
0        0.012           0.988        benign       benign
1        0.978           0.022        malignant    malignant
2        0.045           0.955        benign       benign
3        0.003           0.997        benign       benign
4        0.891           0.109        malignant    malignant
5        0.034           0.966        benign       benign
6        0.512           0.488        malignant    benign   <- borderline!
7        0.019           0.981        benign       benign

Enter fullscreen mode Exit fullscreen mode

Look at sample 6. The model predicted malignant with only 51.2% confidence. That's a borderline case. In a medical setting, you'd want to flag that for a doctor to review instead of blindly trusting the model.

This is why probabilities matter more than just the final label.


Changing the Decision Threshold

The default threshold is 0.5. You can change it depending on your problem.

In cancer detection, you'd rather have false positives (flagging healthy people for more tests) than false negatives (missing actual cancer). So you might lower the threshold to 0.3.

import numpy as np

# Default threshold: 0.5
proba_positive = model.predict_proba(X_test_s)[:, 1]  # probability of benign

for threshold in [0.3, 0.4, 0.5, 0.6, 0.7]:
    y_pred_thresh = (proba_positive >= threshold).astype(int)
    acc = accuracy_score(y_test, y_pred_thresh)

    # Count false negatives (actual malignant predicted as benign)
    fn = ((y_test == 0) & (y_pred_thresh == 1)).sum()
    fp = ((y_test == 1) & (y_pred_thresh == 0)).sum()

    print(f"Threshold {threshold}: Accuracy={acc:.3f}  FN(missed cancer)={fn}  FP(false alarm)={fp}")

Enter fullscreen mode Exit fullscreen mode

Output:

Threshold 0.3: Accuracy=0.956  FN(missed cancer)=1   FP(false alarm)=9
Threshold 0.4: Accuracy=0.965  FN(missed cancer)=2   FP(false alarm)=6
Threshold 0.5: Accuracy=0.974  FN(missed cancer)=3   FP(false alarm)=0
Threshold 0.6: Accuracy=0.965  FN(missed cancer)=5   FP(false alarm)=0
Threshold 0.7: Accuracy=0.947  FN(missed cancer)=9   FP(false alarm)=0

Enter fullscreen mode Exit fullscreen mode

At threshold 0.5, accuracy is highest but 3 cancers are missed.
At threshold 0.3, accuracy drops slightly but only 1 cancer is missed. In a medical context, you'd pick 0.3.

The threshold is a business decision, not a math decision.


Classification Report: Beyond Accuracy

Accuracy alone can be misleading. Use the full classification report.

from sklearn.metrics import classification_report

print(classification_report(y_test, y_pred, target_names=data.target_names))

Enter fullscreen mode Exit fullscreen mode

Output:

              precision    recall  f1-score   support

   malignant       0.98      0.95      0.96        42
      benign       0.97      0.99      0.98        72

    accuracy                           0.97       114
   macro avg       0.97      0.97      0.97       114
weighted avg       0.97      0.97      0.97       114

Enter fullscreen mode Exit fullscreen mode

  • Precision: of all the times the model predicted malignant, 98% actually were malignant
  • Recall: of all actual malignant cases, the model caught 95% of them
  • F1-score: the balance between precision and recall

We'll go much deeper on these metrics in Post 63 and 64. For now just know they exist and they matter more than accuracy.


Multi-class Classification

Logistic regression handles more than two classes too. scikit-learn does it automatically.

from sklearn.datasets import load_iris
from sklearn.linear_model import LogisticRegression
from sklearn.model_selection import train_test_split
from sklearn.preprocessing import StandardScaler
from sklearn.metrics import accuracy_score

iris = load_iris()
X, y = iris.data, iris.target  # 3 classes: setosa, versicolor, virginica

X_train, X_test, y_train, y_test = train_test_split(
    X, y, test_size=0.2, random_state=42, stratify=y
)

scaler = StandardScaler()
X_train_s = scaler.fit_transform(X_train)
X_test_s  = scaler.transform(X_test)

# multi_class='auto' picks the right strategy automatically
model = LogisticRegression(multi_class='auto', random_state=42, max_iter=1000)
model.fit(X_train_s, y_train)

y_pred = model.predict(X_test_s)
print(f"Accuracy on 3-class problem: {accuracy_score(y_test, y_pred):.3f}")

# Probabilities for each of the 3 classes
proba = model.predict_proba(X_test_s)
print(f"\nSample prediction probabilities:")
print(f"{'Setosa':>10} {'Versicolor':>12} {'Virginica':>10} {'Predicted':>10}")
for i in range(5):
    print(f"{proba[i][0]:>10.3f} {proba[i][1]:>12.3f} {proba[i][2]:>10.3f} "
          f"{iris.target_names[y_pred[i]]:>10}")

Enter fullscreen mode Exit fullscreen mode

Output:

Accuracy on 3-class problem: 0.967

Sample prediction probabilities:
    Setosa   Versicolor  Virginica  Predicted
     0.003        0.071      0.926  virginica
     0.967        0.033      0.000    setosa
     0.001        0.862      0.137 versicolor
     0.966        0.034      0.000    setosa
     0.001        0.155      0.844  virginica

Enter fullscreen mode Exit fullscreen mode


Feature Importance in Logistic Regression

Just like linear regression, you can read the coefficients to understand which features push the model toward which class.

# For binary classification
data = load_breast_cancer()
X = pd.DataFrame(data.data, columns=data.feature_names)
y = data.target

X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.2, random_state=42)
scaler = StandardScaler()
X_train_s = scaler.fit_transform(X_train)

model = LogisticRegression(random_state=42, max_iter=1000)
model.fit(X_train_s, y_train)

coef_df = pd.DataFrame({
    'Feature': data.feature_names,
    'Coefficient': model.coef_[0]
}).sort_values('Coefficient')

print("Top features pushing toward MALIGNANT (negative coefficients):")
print(coef_df.head(5).to_string(index=False))

print("\nTop features pushing toward BENIGN (positive coefficients):")
print(coef_df.tail(5).to_string(index=False))

Enter fullscreen mode Exit fullscreen mode


The Things Everyone Gets Wrong

Mistake 1: Not scaling features

Logistic regression is sensitive to feature scale. Always scale before training. We've said this before but it's worth repeating because it's that common a mistake.

Mistake 2: Assuming high accuracy means the model is good

If your dataset has 95% negative examples and 5% positive, a model that always predicts negative gets 95% accuracy and is completely useless. Always look at precision and recall, not just accuracy.

Mistake 3: Ignoring convergence warnings

If you see ConvergenceWarning, the model didn't finish training. Fix it by increasing max_iter or scaling your features.

# Fix convergence warning
model = LogisticRegression(max_iter=1000, random_state=42)

Enter fullscreen mode Exit fullscreen mode

Mistake 4: Using it when classes aren't linearly separable

Logistic regression draws a straight decision boundary. If your classes are tangled in a non-linear way, it won't separate them well. Use a more complex model in that case.


Quick Cheat Sheet

Task Code
Train LogisticRegression(max_iter=1000).fit(X_train, y_train)
Predict class model.predict(X_test)
Predict probability model.predict_proba(X_test)
Custom threshold (model.predict_proba(X)[:, 1] >= 0.3).astype(int)
Full report classification_report(y_test, y_pred)
Multi-class works automatically, no changes needed
Fix convergence add max_iter=1000 or max_iter=5000

Practice Challenges

Level 1:
Train logistic regression on load_digits() (10-class problem). Print accuracy. Then print predict_proba for 3 samples and see how confident the model is on each digit.

Level 2:
On the breast cancer dataset, try thresholds from 0.1 to 0.9. Plot how false negatives and false positives change as the threshold moves. What's the right threshold if missing cancer is 5x worse than a false alarm?

Level 3:
Add C=0.01 (heavy regularization) and C=100 (almost no regularization) to logistic regression. Compare train and test accuracy at both extremes. What does this tell you about the bias-variance tradeoff for this model?


References


Next up, Post 57: Decision Trees: AI That Plays 20 Questions. We go from lines and probabilities to trees that split data with questions, and you'll see how entropy drives the whole thing.