Skip to content

Remove zero SoC placeholders from tablet records - #271

Merged
Seungpyo1007 merged 1 commit into
developfrom
fix/tablet-soc-values
Sep 25, 2026
Merged

Seungpyo1007 merged 1 commit into
developfrom
fix/tablet-soc-values

Conversation

@Seungpyo1007

@Seungpyo1007 Seungpyo1007 commented Sep 25, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Removed the literal "0" SoC placeholder from 53 tablet records: 38 now omit soc, and 15 use null where another record in the same folder has a specific SoC.
  • Kept generic or ambiguous SoC references unchanged when the tablet's own sourced raw fields do not identify an exact vendor and model. No SoC records were edited.

Counts

Measure Before After
Tablet records with non-null soc 2,513 2,460
Tablet records with soc: "0" 53 0
Tablet values lacking a matching data/soc slug 0 0
Remaining generic or ambiguous tablet SoC references 313 313

The strict foreign-key count is zero because the SoC dataset itself contains placeholder slugs, including 0 and qualcomm-snapdragon. These placeholders do not establish a specific chip.

Mapping table

Sourced raw chipset New SoC slug Tablet records
No unambiguous vendor-and-model matches found ? 0

Placeholder SoC slugs and remaining references

Tablet counts are after this change. Smartphone counts are read from HEAD:data/smartphone, which is outside this sparse checkout. The 0 row shows its zero tablet references after cleanup and unchanged smartphone references.

SoC slug Tablets before Tablets after Smartphones
0 53 0 3610
qualcomm-snapdragon 49 49 1700
quad-core-1-2-ghz 27 27 157
dual-core-1-6-ghz-cortex-a9 23 23 12
dual-core-1-5-ghz-cortex-a9 17 17 8
1-0-ghz-cortex-a8 15 15 14
exynos 10 10 100
mediatek 10 10 58
quad-core 10 10 22
quad-core-1-2-ghz-cortex-a7 10 10 25
1-2-ghz-cortex-a8 9 9 10
mediatek-helio 9 9 245
qualcomm-snapdragon-s4-pro 9 9 39
intel-atom 8 8 5
quad-core-1-0-ghz-cortex-a7 7 7 4
qualcomm-snapdragon-s3 7 7 42
quad-core-1-6-ghz-cortex-a9 6 6 2
1-0-ghz 5 5 118
dual-core-1-5-ghz 5 5 40
dual-core-1-6-ghz 5 5 3
1-2-ghz 4 4 13
800-mhz 4 4 53
dual-core-1-3-ghz 4 4 35
spice-mobile-platform-2013 4 4 21
1-2-ghz-cortex-a9 3 3 2
dual-core-1-3-ghz-cortex-a7 3 3 9
intel-atom-z3560-or-z3580 3 3 2
quad-core-1-2-ghz-cortex-a9 3 3 1
quad-core-1-3-ghz 3 3 146
quad-core-1-3-ghzquad-core-1-2-ghz-usa-model 3 3 1
qualcomm-snapdragon-s2 3 3 6
zte-mobile-platform-2012 3 3 8
1-0-ghz-cortex-a5 2 2 7
1-22-ghz-cortex-a8 2 2 1
1-5-ghz 2 2 2
alcatel-mobile-platform-2014 2 2 10
dual-core-1-0-ghz-cortex-a5 2 2 3
dual-core-1-0-ghz-cortex-a9 2 2 7
dual-core-1-2-ghz 2 2 106
huawei-mobile-platform-2011 2 2 30
nvidia-tegra-2 2 2 8
quad-core-1-1-ghz 2 2 13
quad-core-1-3-ghz-cortex-a7 2 2 125
quad-core-1-5-ghz-cortex-a7 2 2 11
qualcomm 2 2 206
800-mhz-scorpion 1 1 2
dual-core-1-2-ghz-marvell 1 1 1
intel-atom-x3 1 1 1
panasonic-mobile-platform-2011 1 1 5
pantech-mobile-platform-2008 1 1 3
quad-core-1-5-ghz 1 1 26

The remaining generic or ambiguous values have no exact vendor-and-model match in their own sourced raw chipset fields.

Validation

PYTHONIOENCODING=utf-8 python -m app.validate passed.

Refs #1

@github-actions github-actions Bot added data Dataset changes enhancement New feature or request labels Sep 25, 2026
@Seungpyo1007 Seungpyo1007 added bug Something isn't working and removed enhancement New feature or request labels Sep 25, 2026
@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

604 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" : 543
    "Yellow" : 61
    "Red" : 0
Loading
Category Distribution Total 🟢 🟡 🔴 🟢 %
brand 🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨🟨 13 7 6 0 53.8%
soc 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 20 20 0 0 100.0%
smartphone 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨 38 37 1 0 97.4%
tablet 🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 63 10 53 0 15.9%
watch 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 4 4 0 0 100.0%
pda 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 1 1 0 0 100.0%
gpu 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨 75 74 1 0 98.7%
cpu 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 390 390 0 0 100.0%
All 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨 604 543 61 0 89.9%

Full-dataset baseline

106245 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" : 24045
    "Yellow" : 81104
    "Red" : 1096
Loading
Category Distribution Total 🟢 🟡 🔴 🟢 %
brand 🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨 207 122 85 0 58.9%
soc 🟩🟨🟨🟨🟨🟨🟥🟥🟥🟥🟥🟥 2097 251 824 1022 12.0%
smartphone 🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 93396 17931 75397 68 19.2%
tablet 🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 3455 291 3163 1 8.4%
watch 🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥 433 43 386 4 9.9%
pda 🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨 140 83 57 0 59.3%
gpu 🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨 2093 1274 819 0 60.9%
cpu 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨🟥 4424 4050 373 1 91.5%
All 🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟥 106245 24045 81104 1096 22.6%

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.

@Seungpyo1007
Seungpyo1007 merged commit a038fc0 into develop Sep 25, 2026
5 checks passed
@Seungpyo1007
Seungpyo1007 deleted the fix/tablet-soc-values branch September 25, 2026 06:46
@github-project-automation github-project-automation Bot moved this from In Progress to Done in TechAPI-Project Sep 25, 2026
@TechEngineBot

Copy link
Copy Markdown
Member

TechEngine change review: PASS

Check Result
python -m app.validate PASS
New hard integrity anomalies vs PR base 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 53 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 0 0 0 0 0 0

Changed record examples

tablet modified

  • tablet/amazon/2019/fire-hd-10/amazon-fire-hd-10-aitoolbuzz-673-2gb-32gb-2g.json - Amazon Fire HD 10 (2019)
  • tablet/amazon/2021/fire-hd-10/amazon-fire-hd-10-aitoolbuzz-674-3gb-32gb-2g.json - Amazon Fire HD 10 (2021)
  • tablet/asus/2016/zenpad-z10-zt500kl/asus-zenpad-z10-zt500kl-aitoolbuzz-1121-3gb-32gb-4g-lte.json - Asus Zenpad Z10 ZT500KL
  • tablet/asus/2016/zenpad-z8/asus-zenpad-z8-aitoolbuzz-1122-2gb-16gb-4g-lte.json - Asus Zenpad Z8
  • tablet/asus/2017/zenpad-3-8-0-z581kl/asus-zenpad-3-8-0-z581kl-aitoolbuzz-1109-4gb-32gb-4g-lte.json - Asus Zenpad 3 8.0 Z581KL
  • tablet/asus/2017/zenpad-3s-10-z500kl/asus-zenpad-3s-10-z500kl-aitoolbuzz-1110-4gb-32gb-4g-lte.json - Asus Zenpad 3S 10 Z500KL
  • tablet/doogee/2024/t10w/doogee-t10w-aitoolbuzz-2356-4gb-128gb-4g-lte.json - Doogee T10W
  • tablet/doogee/2025/u11-pro/doogee-u11-pro-aitoolbuzz-2373-6gb-256gb-4g-lte.json - Doogee U11 Pro
  • tablet/honor/2021/tablet-v7-pro/honor-tablet-v7-pro-8gb.json - Tablet V7 Pro
  • tablet/honor/2021/tablet-v7-pro/honor-tablet-v7-pro-aitoolbuzz-3023-8gb-128gb-5g.json - Honor Tablet V7 Pro
  • tablet/honor/2021/tablet-v7-pro/honor-tablet-v7-pro-allphones-2723-8gb-128gb-5g.json - Honor Tablet V7 Pro
  • tablet/honor/2021/tablet-v7/honor-tablet-v7-6gb.json - Tablet V7
  • tablet/honor/2021/tablet-v7/honor-tablet-v7-aitoolbuzz-3022-8gb-128gb-5g.json - Honor Tablet V7
  • tablet/honor/2021/tablet-v7/honor-tablet-v7-allphones-2821-8gb-128gb-5g.json - Honor Tablet V7
  • tablet/honor/2023/pad-v8/honor-pad-v8-aitoolbuzz-2978-8gb-128gb-4g-lte.json - Honor Pad V8
  • ... 38 more

Heuristic review

  • 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 122 85 0 207 58.9%
soc 2097 193 1904 0 2097 9.2%
smartphone 93396 17501 75895 0 93396 18.7%
tablet 3455 273 3182 0 3455 7.9%
watch 433 39 394 0 433 9.0%
pda 140 74 66 0 140 52.9%
gpu 2093 1028 1065 0 2093 49.1%
cpu 4424 2869 1555 0 4424 64.9%
all 106245 22099 84146 0 106245 20.8%

Warning

Tracked verified coverage is below 50% for tablet 7.9% (273/3455), watch 9.0% (39/433), soc 9.2% (193/2097), smartphone 18.7% (17501/93396), all 20.8% (22099/106245), gpu 49.1% (1028/2093).
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

  • The integrity gate blocks only hard anomalies introduced by this PR relative to its merge base.
  • 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 (PR head compared with PR base)
loaded CPU=4424 GPU=2093
Integrity section Flagged lines
structural 20
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) 155
GPU cross-source ratio outliers + sanity 18

Seungpyo1007 added a commit that referenced this pull request Sep 26, 2026
…soc "0" on watches

The Galaxy Watch series spec table names each model's chip: W920 (Watch4,
Watch4 Classic, Watch5, Watch5 Pro), W930 (Watch6, Watch6 Classic), W1000
(Watch7, Ultra). Add Exynos W920/W930 from Wikipedia's Exynos table. The
other 18 watch records had the placeholder soc "0" with nothing naming a
chip, so drop it, as #271 did for tablets.

Refs #296
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working data Dataset changes

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants