|
1 | 1 | # data/ — curated dataset |
2 | 2 |
|
3 | | -These JSON files are the **curated, validated** records the API serves. Layout is |
4 | | -singular folder names, organised by brand: |
| 3 | +These JSON files are the **curated, validated** records the API serves: one |
| 4 | +file per record, named `<slug>.json`, in singular category folders. |
5 | 5 |
|
6 | 6 | ``` |
7 | | -brand/<slug>.json |
8 | | -soc/<manufacturer>/<slug>.json |
9 | | -smartphone/<brand>/<slug>.json |
10 | | -gpu/<manufacturer>/<year>/<segment>/<slug>.json # GPUs are split by release year then segment (consumer | enterprise) |
11 | | -cpu/<manufacturer>/<year>/<segment>/<slug>.json # CPUs split by release year then segment (consumer | enterprise) |
| 7 | +brand/<country>/<slug>.json # country code in lower case, or unknown/ |
| 8 | +soc/<manufacturer>/<year>/<slug>.json |
| 9 | +cpu/<manufacturer>/<year>/<consumer|enterprise>/<slug>.json |
| 10 | +gpu/<manufacturer>/<year>/<consumer|enterprise>/<slug>.json |
| 11 | +smartphone/<brand>/<year>/<slug>.json # or <year>/<base_model>/<slug>.json |
| 12 | +tablet/<brand>/<year>/<base_model>/<slug>.json # watch/, pda/, laptop/ and monitor/ are the same |
| 13 | +device_catalog/<brand>/<slug>.json # device identities with no known release date |
| 14 | +software/<prefix>/<slug>.json # prefix = first two characters of the slug |
| 15 | +website/<prefix>/<slug>.json |
| 16 | +_verify/ # not records: see below |
12 | 17 | ``` |
13 | 18 |
|
14 | | -GPU `<segment>` is: |
| 19 | +The [root README](../README.md#layout) has the same table with file counts and |
| 20 | +an example for each category. |
| 21 | + |
| 22 | +The `consumer` / `enterprise` folder is a coarse split. For GPUs: |
15 | 23 | * `consumer` — gaming/desktop & laptop dGPUs (GeForce GTX/RTX, Radeon RX/R9/HD, Arc, Voodoo, MTT S60/S70/S80, …) |
16 | 24 | * `enterprise` — datacenter compute, AI accelerators, workstation pro cards (Tesla, A100/H100/B200, Quadro/RTX A/RTX PRO, Radeon Pro W, Instinct MI, MTT S3000/S4000, Vega Frontier, AI-focused TITAN V/RTX, …) |
17 | 25 |
|
| 26 | +For CPUs, `enterprise` holds server and most HEDT parts. The record's own |
| 27 | +`segment` field is finer: `desktop`, `laptop`, `hedt` or `server`. |
| 28 | + |
| 29 | +`_verify/` holds the verification ledger (`ledger.jsonl`), the status aggregate |
| 30 | +(`status.json`) and the caches under `state/`. TechEngine's verify tools write |
| 31 | +them; don't edit them by hand. |
| 32 | + |
18 | 33 | > ⚠️ **This is a curated subset — NOT an exhaustive list of every device/chip.** |
19 | | -> It is hand-verified and intentionally partial. Breadth is expanded out-of-band |
20 | | -> through an internal pipeline that publishes curated records here after review; |
21 | | -> each record carries `source_urls`. Don't assume a device is missing-by-error — |
22 | | -> it may simply not be curated yet. |
| 34 | +> It is intentionally partial. New records come from TechEngine's collectors and |
| 35 | +> land here through a reviewed PR; each record carries `source_urls`, and |
| 36 | +> `verified` says whether it has passed verification. Don't assume a device is |
| 37 | +> missing-by-error — it may simply not be curated yet. |
23 | 38 |
|
24 | 39 | Validate after edits: `python -m app.validate`. Add only real, sourced models. |
0 commit comments