Repository navigation
fix(data): merge 18 duplicate Intel Atom CPU records - #321
Conversation
The strict integrity gate (integrity_check.py --strict) has been hard-blocking weekly-refresh for at least the last 5 runs: 18 Intel Atom CPUs were each imported twice under two slugs, once without an "intel-" prefix (Wikipedia- sourced) and once with it (a later Kaggle-dataset import). These were not harmless duplicates - the two sides disagreed on release_date, threads and other fields for most pairs. Cross-checked every pair against https://en.wikipedia.org/wiki/List_of_Intel_Atom_processors: - release_date: the "atom-X" (Wikipedia) record matches the table almost exactly, often to the day. The "intel-atom-X" record's dates are frequently wrong, in two cases (Z3530, Z3560) off by a full 8 years. - threads: Wikipedia lists Hyper-Threading support for 17 of these 18 SKUs (only D2500 does not). The "intel-atom-X" record already encoded threads = 2x cores; the "atom-X" record wrongly had threads = cores for 16 of them. - clock/tdp/cache/socket/process_node: spot-checked the same way; kept whichever side matched Wikipedia (mostly the "atom-X" side, e.g. Z3560's "intel-atom-z3560" record had clock_ghz=1.0 vs Wikipedia's stated 1.83). Each merged record keeps the union of both sides' source_urls and survives under the shorter "atom-X" slug/path. `integrity_check.py --strict` now reports 0 hard anomalies. Closes #296
🔎 Data verification — Tier 0 (offline existence/trust)Scored by 12/12 categories ? 191,819 records ? diff base develop@c317ed9 Changed records in this PR18 record(s) assessed. %%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
title Verification bands — all records
"Green" : 18
"Yellow" : 0
"Red" : 0
Full-dataset baseline191819 record(s) assessed. %%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
title Verification bands — all records
"Green" : 32772
"Yellow" : 157992
"Red" : 1055
Hard violations (forced red):
green = authoritative source + complete + consistent · yellow = plausible, needs confirmation · red = sparse/weak source or a hard contradiction. Promotion to |
TechEngine change review: PASS12/12 categories ? 191,819 records ? diff base develop@c317ed9
Changed data
Changed record examplescpu modified
cpu deleted
Heuristic review
|
TechEngine validation stats: PASS12/12 categories ? 191,819 records ? diff base develop@c317ed9
Data summary
Warning Tracked verified coverage is below 50% for monitor 0.0% (0/882), software 0.8% (358/42493), laptop 5.3% (105/1995), tablet 8.3% (288/3459), soc 13.4% (284/2117), all 16.8% (32257/191819), smartphone 18.8% (17581/93407), website 19.0% (7635/40084), and 1 more. Validation notes
Key output:
|
What & why
TechEngine's
integrity_check.py --strictgate has been hard-blockingweekly-refreshfor at least the last 5-6 runs (all failures/cancellations since 2026-08-31), previously misdiagnosed as CI infra flakiness. The real cause: 18 Intel Atom CPUs were each imported twice under two slugs — once without anintel-prefix (Wikipedia-sourced, older) and once with it (a later Kaggle-dataset import) — and the strict gate treats same-name CPU records as a hard anomaly.These were not harmless exact duplicates; the two sides disagreed on
release_date,threads, and other fields for most pairs.How each pair was resolved
Cross-checked every pair against https://en.wikipedia.org/wiki/List_of_Intel_Atom_processors:
atom-X(Wikipedia-cited) record matches the table almost exactly, often to the exact day. Theintel-atom-Xrecord's dates are frequently wrong — in two cases (Z3530, Z3560) off by a full 8 years (claiming 2022 releases for 2014 chips).intel-atom-Xrecord already correctly encodedthreads = 2× cores; theatom-Xrecord wrongly hadthreads = coresfor 16 of them (missing HT).atom-Xside (e.g. theintel-atom-z3560record hadbase_clock_ghz=1.0vs Wikipedia's stated 1.83 GHz).Each merged record keeps the union of both sides'
source_urls, survives under the shorteratom-Xslug/file path, and staysverified: true. The corresponding stale dump pages for the 18 deletedintel-atom-Xslugs are removed too (the dump generator doesn't prune records that no longer exist, so those pages would otherwise have stayed orphaned).Verification
python integrity_check.py <data> --strict(the exact commandweekly-refreshruns) now reports 0 hard anomalies, down from 18.Closes #296