How often does Brain Engine recalculate risk scores?

Brain Engine runs on PythonAnywhere cron every 60 minutes, recalculating all 7 risk signals for all 40 monitored cities. Each full cycle takes 45–90 seconds. Additionally, any M5.5+ earthquake detected in the USGS significant events feed triggers an immediate out-of-cycle recalculation within 3 minutes.

What happens if an API source is unavailable during a Brain Engine run?

Brain Engine implements graceful degradation: if an API (e.g., Open-Meteo) fails to respond within 90 seconds, the previous cached value is retained and the affected signal is flagged as stale. The composite score is calculated with remaining available signals, and the dashboard displays a data-age indicator warning users that one signal may be outdated.

Every Hour, A Machine Checks the Planet: Inside Brain Engine's Automation Cycle

Name: Brain Dashboard Risk Data — Dhaka, Bangladesh
Creator: Pandita Data
Keywords: brain dashboard, pandita data, Dhaka, Bangladesh, geohazard, pandita data, risk dashboard, live risk scores, natural disaster intelligence

← ALL ARTICLES

// LIVE OVERVIEW MAP — REAL-TIME DATA

DATA: USGS · NASA FIRMS · NOAA SWPC · OPEN-METEO · COPERNICUS SAR

↗ OPEN FULL SCREEN

Every hour, without fail, a silent digital sentinel awakens on PythonAnywhere servers. It scans 30+ live 3D hazard simulations across 500+ monitored cities. When an earthquake hits M5.5 or above, it doesn't wait for the next scheduled cycle—it breaks protocol and broadcasts immediately. This is the Brain Engine: Pandita Data's automated nervous system that keeps your risk scores breathing in real time.

THE SCHEDULER ARCHITECTURE

At the heart of Pandita Data's intelligence delivery is scheduler.py, a Python automation worker running on PythonAnywhere's cron infrastructure. Every 60 minutes, this process awakens to fetch fresh hazard telemetry, recompute AI risk scores, and push updates to your Brain Dashboard. The system operates on a three-tier data pipeline: live sensor ingestion (seismic networks, weather APIs, satellite feeds) → SQLite local cache → REST API distribution to front-end clients.

What makes this architecture resilient is redundancy. If one city's calculation stalls, parallel execution threads continue processing others. Failed API calls queue for retry within 15 minutes. The entire cycle completes in under 8 minutes, leaving a 52-minute buffer for network latency and system hiccups.

⚙️

Hourly Scheduler Loop

scheduler.py triggers every 60 minutes via PythonAnywhere cron. Fetches raw hazard data from 15+ global monitoring networks, validates against historical baselines, and queues updates for REST API distribution.

Core Process

🔥

M5.5+ Immediate Override

When seismic magnitude crosses 5.5, the scheduler abandons its hourly cadence. A dedicated interrupt handler triggers within 90 seconds, triggering emergency city risk recalculation and push notification to all active users.

Emergency Protocol

📊

Parallel City Execution

Rather than calculate cities sequentially, the engine spins up 8 parallel threads. Tokyo, Mumbai, Los Angeles, and Istanbul risk scores compute simultaneously, maximizing throughput and minimizing latency for your Brain Dashboard.

Performance Layer

WHAT HAPPENS EACH HOUR

500+

Cities Monitored

8 Min

Compute Cycle Time

30+

Hazard Types Scanned

99.7%

Uptime (12-month)

The Hourly Workflow

At the top of each hour (00:00, 01:00, 02:00 UTC), scheduler.py awakens. It connects to SQLite's local cache and pulls the latest risk coefficients. Simultaneously, REST API calls fan out to USGS, JMA, BMKG, and other seismic networks. Weather APIs deliver wind speed, precipitation, and barometric pressure. Satellite thermal data surfaces active volcanic and wildfire signatures. All raw inputs feed into the Brain Engine's AI risk model—a trained ensemble that weighs magnitude, depth, proximity, soil type, and historical precedent. Scores recalculate across all 30+ simulation modules. Results write back to SQLite. The REST API publishes fresh risk values to the front-end, refreshing your Brain Dashboard within seconds.

MAJOR EVENT TRIGGERS

Seismic M5.5+ Override

Immediate re-execution of affected region's risk scores; push notifications sent within 90 seconds.

Volcanic Thermal Spike (+15°C)

Unscheduled recalculation for volcanic hazard zones; satellite imagery cross-checks via thermal anomaly detection.

Flood Risk Elevation (>2σ)

Rainfall forecast models re-run for affected watersheds; Disaster Report updates automatically.

API Retry Exhaustion

🧠 OPEN BRAIN DASHBOARD

Every Hour, A Machine Checks the Planet: Inside Brain Engine's Automation Cycle

THE SCHEDULER ARCHITECTURE

WHAT HAPPENS EACH HOUR

MAJOR EVENT TRIGGERS

RELATED ARTICLES