How to Compare AI Sector Heat Across Time Windows
Resumen
Pixel shares a practical guide to comparing AI concept heat across rolling windows from 1 hour to 3 days. It demonstrates a capture function and validation checks using Lava’s concept heat board, helping the community distinguish real momentum shifts from misleading differences between timeframes.
DEV Community
Sector Heat Rolling Window Comparison: Unit-Testing AI Theme Heat from 1h to 3d
An AI-related concept ranks second on the one-hour heat board and eleventh on the three-day board. Is that a sudden burst, or a theme cooling off? Usually it is neither. It is two rolling windows measuring different things, and the gap only becomes a story when someone compares them without checking that the comparison is valid. This article treats a sector heat rolling window comparison like code under test. Instead of a reading checklist, we write assertions: a capture function that pulls all windows for one theme, a set of checks that must pass before anyone describes the result, and a small vocabulary for describing the shape once it does. The examples use Lava's concept heat board, and every number is illustrative. The Data: Concept Heat Board Windows The entry point is GET /hot/concepts, exposed to agents as the MCP tool get_market_hot_concepts. Parameter / field Meaning Default Note window 1h, 4h, 18h, 24h, 3d 24h no 7d on concepts min_score count only mentions from institutions/KOLs scoring at least this unset scores roughly 450–1500; ~1000 is mid, 1050 is about the top 10% limit 1–200 50 no offset mentions times the concept was mentioned in the window — concept-level count agencies distinct institutions/KOLs mentioning it — deduplicated by anonymous agency_id heat_chg_1d, heat_chg_3d, heat_z20 statistics — exact formulas in OpenAPI Three properties matter for cross-window work: Windows roll back from meta.server_time. 1h is the last hour, 3d the last 72 hours. Short windows are more sensitive to a single long post or one concentrated burst. The longest concept window is 3d. For weekly or longer views, switch to the daily panel /panel/daily with type=concept. Overly generic terms are removed before ranking. Names on the board are canonical and can be passed to drill-down endpoints. Removed generic terms never appear in any window, so a cross-window gap is never "explained" by them. The board refreshes about every 2 minutes. The concept member ranking /concepts/stocks refreshes about every 10 minutes. That timing gap alone explains many "the numbers don't match" reports. Step 1: Capture All Windows in One Round # ai_theme_windows.py - illustrative; base URL and token are placeholders
import os, requests
BASE = os.environ.get("LAVA_BASE", "/subscribe/v1")
HEADERS = {"Authorization": "Bearer " + os.environ.get("LAVA_API_KEY", "")}
WINDOWS = ("1h", "4h", "18h", "24h", "3d")
TARGET = ""
def capture(target, min_score=None, limit=200):
snap = {}
for w in WINDOWS:
params = {"window": w, "limit": limit}
if min_score is not None:
params["min_score"] = min_score
resp = requests.get(BASE + "/hot/concepts", params=params,
headers=HEADERS, timeout=60).json()
assert resp["ok"], resp.get("code")
data = resp["data"]
rows = data if isinstance(data, list) else data.get("list", [])
# concept-name column assumed to be "concept"; confirm in OpenAPI
hit = next(((i + 1, r) for i, r in enumerate(rows)
if r.get("concept") == target), None)
snap[w] = {
"params": params,
"server_time": resp["meta"]["server_time"],
"request_id": resp["meta"]["request_id"],
"rank": hit[0] if hit else None,
"mentions": hit[1].get("mentions") if hit else None,
"agencies": hit[1].get("agencies") if hit else None,
"heat_z20": hit[1].get("heat_z20") if hit else None,
}
return snap
snap = capture(TARGET)
A rank of None means "not in the top 200 for this window". Record it that way, never as zero. Step 2: Assertions That Must Pass Before Interpretation import pandas as pd
def check(snap):
times = [pd.Timestamp(s["server_time"]) for s in snap.values()]
assert max(times) - min(times) < pd.Timedelta(minutes=5), "windows from different rounds"
scores...

Powered by Readybot.io