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

推荐订阅源

A
About on SuperTechFans
G
Google Developers Blog
L
LangChain Blog
aimingoo的专栏
aimingoo的专栏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
云风的 BLOG
云风的 BLOG
小众软件
小众软件
月光博客
月光博客
Recent Announcements
Recent Announcements
人人都是产品经理
人人都是产品经理
P
Proofpoint News Feed
博客园 - 聂微东
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
雷峰网
雷峰网
The Cloudflare Blog
博客园_首页
美团技术团队
大猫的无限游戏
大猫的无限游戏
B
Blog
IT之家
IT之家
Jina AI
Jina AI
H
Hackread – Cybersecurity News, Data Breaches, AI and More
C
Check Point Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知

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
When Information Hits a Wall: Barriers in Cellular Automata
John Samuel · 2026-04-27 · via DEV Community

TL;DR: Add one frozen cell to a cellular automaton and watch the entire pattern reshape itself. This post explores what happens when you introduce a single barrier into elementary CAs — and why it matters for both theory and real-world modeling.

What happens when a single cell in a cellular automaton refuses to change?

In elementary cellular automata (ECAs), every cell updates each generation based on its neighbors and a deterministic rule. Patterns emerge, spread, and evolve across the grid in beautiful, often chaotic ways. But introduce one frozen cell — one immutable point that never updates — and the entire system transforms.

This simple constraint acts like matter in an otherwise purely computational space, blocking information flow and reshaping how patterns propagate.


🧱 The Barrier Concept

A barrier is remarkably simple to define: mark one cell as frozen.

While every other cell continues updating according to the automaton's rule, this single cell remains locked in its initial state. It doesn't compute. It doesn't respond to neighbors. It just sits there, unchanging.

The automaton must work around this obstacle. Information flowing through the grid can't pass through the barrier — it reflects, splits, or terminates at this boundary.

Think of it like dropping a rock into a stream: the water doesn't stop, but its flow pattern is permanently altered.

Rule 195

Rule 195

Rule 195 with one cell barrier

Rule 195 with one cell barrier

🔬 Visualizing the Impact: Three Rules, One Barrier

Rule 30 — Chaos Interrupted

Rule 30 is famous for its chaotic, random-looking output — so much so that Wolfram used it as a pseudorandom number generator. Place a barrier anywhere in a Rule 30 grid, and you see dramatic sensitivity: patterns on either side of the frozen cell diverge completely, as if two independent automata are running simultaneously.

Rule 110 — Computation Blocked

Rule 110 is remarkable: it's been proven Turing-complete, capable of universal computation. A barrier doesn't just disrupt its pattern — it interrupts the computation itself. Signals that would have propagated and interacted across the grid are halted or reflected, cutting off potential glider collisions and information pathways.

Rule 90 — Symmetry Preserved (Then Broken)

Rule 90 produces beautiful, perfectly symmetric Sierpiński triangle-like patterns under normal conditions. Add a barrier on the central axis, and the symmetry is maintained. Shift it off-center, however, and you get asymmetric reflections — a clean demonstration of how positional context shapes global behavior.


🧪 A Minimal Experiment You Can Run

Here's the core idea in code:

# Elementary CA with a single frozen barrier
RULE = 30
SIZE = 101
BARRIER_POS = SIZE // 3  # Offset from center

grid = [0] * SIZE
grid[SIZE // 2] = 1  # Single active cell at start

def step(row, rule, barrier):
    new_row = []
    for i in range(len(row)):
        if i == barrier:
            new_row.append(row[i])  # Frozen — never updates
        else:
            left   = row[i - 1] if i > 0 else 0
            center = row[i]
            right  = row[i + 1] if i < len(row) - 1 else 0
            index  = (left << 2) | (center << 1) | right
            new_row.append((rule >> index) & 1)
    return new_row

for _ in range(50):
    grid = step(grid, RULE, BARRIER_POS)

Enter fullscreen mode Exit fullscreen mode

The key insight: one if statement is all it takes to turn a computational cell into a physical obstacle.

Try changing BARRIER_POS or swapping RULE to 90 or 110 — the behavioral differences are striking.


💡 Why One Barrier Matters

The single-barrier setup is a case of minimal experimental design. By introducing exactly one constraint, you isolate its effects cleanly — no noise from multiple obstacles or extended walls. Every change in behavior traces directly back to that one frozen cell.

This reveals something profound: cellular automata, despite being abstract computational systems, respond to spatial constraints in ways that feel physical. The barrier doesn't change the rule or the initial conditions — it just occupies space. Yet this spatial occupation transforms global dynamics.

From a research perspective, barriers bridge pure computation and physical simulation:

  • 🔷 Crystal defects in material science — impurities that scatter phonons and electrons
  • 🌊 Obstacles in fluid flow — the same logic underpins lattice-Boltzmann simulations
  • ⚛️ Scattering particles in quantum systems — potential wells and barriers that reflect wave functions

Cellular automata give us a clean, discrete sandbox to study the same phenomenon at minimal cost.


🚀 Try It Interactively

In a universe of pure information, a barrier becomes matter. And matter, it turns out, changes everything.

👉 Explore barriers interactively at CellCosmos

Switch between Rule 30, 90, and 110. Drag the barrier to different positions. Watch how one frozen cell reshapes the entire computation around it.


What rule or barrier position surprised you the most? Drop a comment — I'd love to compare notes!