Skip to content

data(cpu): add 15 Intel Core parts the dataset was missing - #160

Merged
Seungpyo1007 merged 2 commits into
developfrom
data/intel-core-gaps
Aug 12, 2026
Merged

data(cpu): add 15 Intel Core parts the dataset was missing#160
Seungpyo1007 merged 2 commits into
developfrom
data/intel-core-gaps

Conversation

@Seungpyo1007

@Seungpyo1007 Seungpyo1007 commented Aug 12, 2026

Copy link
Copy Markdown
Member

15 Intel Core parts that Wikipedia's desktop and mobile lists document and this dataset had no record of — the first net-new hardware records in a while, each carrying a Tier-1 source.

core-i7-660lm    2010-09  2c/4t  Arrandale        laptop
core-i7-2657m    2011-02  2c/4t  Sandy Bridge-M   laptop
core-i7-2649m    2011-02  2c/4t  Sandy Bridge-M   laptop
core-i7-2629m    2011-02  2c/4t  Sandy Bridge-M   laptop
core-i7-4950hq   2013-06  4c/8t  Haswell-H        laptop
core-i7-5750hq   2015-06  4c/8t  Broadwell-H      laptop
core-i5-5350h    2015-06  2c/4t  Broadwell-H      laptop
core-i7-6970hq   2016-01  4c/8t  Skylake-H        laptop
core-i7-6870hq   2016-01  4c/8t  Skylake-H        laptop
core-i7-6785r    2016-05  4c/8t  Skylake-H        desktop
core-i5-6685r    2016-05  4c/4t  Skylake-H        desktop
core-i5-6585r    2016-05  4c/4t  Skylake-H        desktop
core-i5-8400b    2018-04  6c/6t  Coffee Lake-B    laptop
core-i3-8100h    2018-07  4c/4t  Coffee Lake-H    laptop
core-i3-8100f    2019-01  4c/4t  Coffee Lake-S    desktop

Every required field comes from the source: manufacturer and segment from the page, cores and threads from its Cores (Threads) column, clocks / cache / TDP / process node from the row. The day of month is the only thing the tables do not state, so a month-precise date is written as the 1st rather than inventing a day.

What was deliberately thrown away

The candidate pool started at 400 and finished at 15. Each cut removed a class of wrong record, not a class of inconvenient one:

left
names not matching ours (Phenom X4 9100e vs our amd-phenom-9100e-quad-core — same chip) 169
no Cores (Threads) cell, or a date cell that isn't a date (one held US $384) 128
hybrid generations — Alder Lake onward split P/E cores across separate rowspan'd columns, so the single figure is the P-core count. It read the i9-13900T as 8c/16t; the part is 24c/32t 19
core counts inherited across a brand tier — an i7's rowspan reaching an i5. That is how the i5-10310Y (2c/4t) picks up the i7-10510Y's 4 (8). Inheritance within one tier is the table's normal shorthand and is kept 15

All 15 were checked against the real parts.

Dump

Regenerated for cpus at the pinned engine (d84bcec); collection count 3,977 → 3,992 so the manifest entry updates.

The diff is larger than 15 records because the published dump's verified flags were stale: promotion PRs flip verified in data/ but never refresh site/public/v1, so 3,326 CPU pages were still advertising the old value. This refresh brings them in line. That gap is worth closing properly — promotions should either refresh the affected pages or the site should read verified from the ledger.

python -m app.validate passes.

Closes #1

Wikipedia's Intel Core desktop and mobile lists document these; we had
no record of them. Every required field is read from the source row or
the page it sits on — manufacturer and segment from the page, core and
thread counts from its "Cores (Threads)" column, clocks, cache and TDP
from the row.

The day of month is the one thing the tables do not state, so a
month-precise date is written as the 1st rather than inventing a day.
Rows whose date cell did not parse as a date were dropped, not guessed
at: one of them held "US $384".

Two classes of row are deliberately excluded because their core counts
cannot be trusted:

* Hybrid generations (Alder Lake onward) split P-cores and E-cores into
  separate rowspan'd columns; the single figure picked up for such a
  part is the P-core count. It read the i9-13900T as 8c/16t when the
  part is 24c/32t.
* Rows whose core count is inherited from a rowspan that crosses a
  brand tier — an i7's cell reaching an i5. That is how the i5-10310Y
  (2c/4t) picks up the i7-10510Y's "4 (8)". Within one tier the
  grouping is the table's normal shorthand and is kept.

Refs #1
@TechEngineBot

Copy link
Copy Markdown
Member

🔎 Data verification — Tier 0 (offline existence/trust)

Scored by app.verify; posted by TechEngineBot. Informational only — the structural gate (app.validate) is separate and authoritative for merge.

Changed records in this PR

15 record(s) scored.

%%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
    title Verification bands — all records
    "Green" : 15
    "Yellow" : 0
    "Red" : 0
Loading
Category Distribution Total 🟢 🟡 🔴 🟢 %
cpu 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 15 15 0 0 100.0%
All 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 15 15 0 0 100.0%

Full-dataset baseline

105757 record(s) scored.

%%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
    title Verification bands — all records
    "Green" : 21328
    "Yellow" : 83228
    "Red" : 1201
Loading
Category Distribution Total 🟢 🟡 🔴 🟢 %
brand 🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 207 24 183 0 11.6%
soc 🟩🟨🟨🟨🟨🟨🟥🟥🟥🟥🟥🟥 2104 146 844 1114 6.9%
smartphone 🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 93396 17382 75934 80 18.6%
tablet 🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 3455 218 3236 1 6.3%
watch 🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 433 18 410 5 4.2%
pda 🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨🟨 140 66 74 0 47.1%
gpu 🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨 2030 810 1220 0 39.9%
cpu 🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟥 3992 2664 1327 1 66.7%
All 🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 105757 21328 83228 1201 20.2%

Hard violations (forced red):

Count Check
1 !boost_ge_base

green = authoritative source + complete + consistent · yellow = plausible, needs confirmation · red = sparse/weak source or a hard contradiction. Promotion to verified runs in the scheduled verify-network workflow.

@TechEngineBot

Copy link
Copy Markdown
Member

TechEngine change review: PASS

Check Result
python -m app.validate PASS
python integrity_check.py TechAPI/data --strict PASS

Changed data

Category Added Modified Deleted Added verified Added unverified Added Kaggle-sourced
brand 0 0 0 0 0 0
soc 0 0 0 0 0 0
smartphone 0 0 0 0 0 0
tablet 0 0 0 0 0 0
watch 0 0 0 0 0 0
pda 0 0 0 0 0 0
gpu 0 0 0 0 0 0
cpu 15 0 0 0 15 0

Changed record examples

cpu added

  • cpu/intel/2010/consumer/core-i7-660lm.json - Intel Core i7-660LM
  • cpu/intel/2011/consumer/core-i7-2629m.json - Intel Core i7-2629M
  • cpu/intel/2011/consumer/core-i7-2649m.json - Intel Core i7-2649M
  • cpu/intel/2011/consumer/core-i7-2657m.json - Intel Core i7-2657M
  • cpu/intel/2013/consumer/core-i7-4950hq.json - Intel Core i7-4950HQ
  • cpu/intel/2015/consumer/core-i5-5350h.json - Intel Core i5-5350H
  • cpu/intel/2015/consumer/core-i7-5750hq.json - Intel Core i7-5750HQ
  • cpu/intel/2016/consumer/core-i5-6585r.json - Intel Core i5-6585R
  • cpu/intel/2016/consumer/core-i5-6685r.json - Intel Core i5-6685R
  • cpu/intel/2016/consumer/core-i7-6785r.json - Intel Core i7-6785R
  • cpu/intel/2016/consumer/core-i7-6870hq.json - Intel Core i7-6870HQ
  • cpu/intel/2016/consumer/core-i7-6970hq.json - Intel Core i7-6970HQ
  • cpu/intel/2018/consumer/core-i3-8100h.json - Intel Core i3-8100H
  • cpu/intel/2018/consumer/core-i5-8400b.json - Intel Core i5-8400B
  • cpu/intel/2019/consumer/core-i3-8100f.json - Intel Core i3-8100F

Heuristic review

  • Added records by manufacturer/brand: intel: 15
  • Added records by source class: other: 15
  • Heuristic warnings: none found.

@TechEngineBot

Copy link
Copy Markdown
Member

TechEngine validation stats: PASS

Data summary

Category Total Verified Unverified Missing verified Tracked Verified % of tracked
brand 207 24 183 0 207 11.6%
soc 2104 146 1958 0 2104 6.9%
smartphone 93396 17384 76012 0 93396 18.6%
tablet 3455 218 3237 0 3455 6.3%
watch 433 18 415 0 433 4.2%
pda 140 66 74 0 140 47.1%
gpu 2030 809 1221 0 2030 39.9%
cpu 3992 2649 1343 0 3992 66.4%
all 105757 21314 84443 0 105757 20.2%

Warning

Tracked verified coverage is below 50% for watch 4.2% (18/433), tablet 6.3% (218/3455), soc 6.9% (146/2104), brand 11.6% (24/207), smartphone 18.6% (17384/93396), all 20.2% (21314/105757), gpu 39.9% (809/2030), pda 47.1% (66/140).
Tracked coverage excludes records missing the verified field; see the Missing verified column for those records.
This does not fail validation. Keep imported records verified: false until manual audit, but treat this as follow-up verification work before relying on the affected categories as curated data.

Validation notes

  • Full advisory outlier listings are suppressed on successful runs because they are dataset-wide and mostly stable between PRs.
  • Failure runs still include a detailed log excerpt for debugging.

Key output:

## app.validate
## integrity_check.py --strict
loaded CPU=3992 GPU=2030
✅ integrity gate: no hard anomalies.
Integrity section Flagged lines
structural 0
CPU name/tier consistency (desktop mainstream only) 0
CPU single>multi (cinebench/geekbench — should be multi>=single) 0
CPU era-vs-score outliers 8
CPU cross-source ratio outliers (possible wrong-variant) 152
GPU cross-source ratio outliers + sanity 18

@Seungpyo1007
Seungpyo1007 merged commit 2950010 into develop Aug 12, 2026
5 checks passed
@Seungpyo1007
Seungpyo1007 deleted the data/intel-core-gaps branch August 12, 2026 05:15
@github-project-automation github-project-automation Bot moved this from In Progress to Done in TechAPI-Project Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

data Dataset changes enhancement New feature or request

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Massive dataset rebuild: CPU + brand + GPU + smartphone + SoC (1989-2026)

2 participants