Skip to content

Audit spec values so DrawTabData is the source of truth #54

Open

Description

@saveenr

Goal

Audit the spec values in DrawTabData so the Explorer can be trusted as the source of truth. The DrawingTabletDocs notes pages now show their specs from this data (generated Specs tabs), and the notes only add context. So a wrong value here shows up wrong everywhere.

Why now

The DrawingTabletDocs Specs rollout compared hand-written notes against this data and found errors on both sides (TheSevenPens/DrawingTabletDocs#67):

TheSevenPens/DrawingTabletDocs#68 lists values the notes have but the data is missing.

Suggested approach

  1. Mechanical checks first (could live in lib/data-quality.ts):
    • values out of range (gamut coverage over 100%, accuracy, tilt, pressure levels)
    • display resolution aspect ratio that doesn't match the active-area aspect ratio
    • pixel density outliers
    • active area larger than the physical size
    • included pen not in pen-compat for that tablet
    • missing core fields (active area, pressure levels, pen technology, release year) for each type
  2. Source checks. For each brand, compare records against the manufacturer's spec page or manual (see Generate tablet links (product page, manual, reviews) from DrawTabData and reconcile with the notes DrawingTabletDocs#76). Record the source used, so the next audit is quicker.
  3. Priority: tablets that have a notes page in DrawingTabletDocs (the 73 pages with a Specs section) first, then current models, then discontinued ones.
  4. Afterwards: regenerate the affected DrawingTabletDocs Specs sections and remove any note values that only existed because the data was wrong.

Open questions

Activity

  1. TheSevenPens commented on Oct 2, 2026

    @TheSevenPens
    Owner

    Mechanical pass (2026-10-02)

    I scanned all 394 tablets. The checks were: range checks, active area against body size, display aspect ratio, pixel density, included pens against pen-compat, missing core fields, and differences between same-size models in one family. 99 tablets have a notes page.

    Fixed in #58

    • 16 tablets shipped a pen that its pen-compat row didn't list. data-quality now checks for this.
    • Cintiq 24, Cintiq 24 touch and Cintiq 16 (2025 models) had body width and height swapped.
    • Intuos Small Bluetooth had no digitizer type.

    Needs a source check (tablets with a notes page)

    • Intuos 12x12 (GD-1212U, also GD-1212R, XD-1212R, XD-1212U): the active area is recorded as 304.8 x 316.8. A 12x12 tablet should be square.
    • Cintiq 21UX 2010 (DTK-2100) and DTZ-1200W: corner accuracy is 4 mm.
    • Intuos 1 (GD-0405U … GD-1218U), UltraPad (UD-0608A … UD-1825R) and SD-510C: no pressure levels or digitizer type.
    • Intuos Medium CTL-690 vs CTH-690: 2048 vs 1024 pressure levels for the same tablet size.
    • 45 color gamut values over 100%, mostly Huion, XP-Pen and UGEE sRGB, are area figures rather than coverage. These go to Display.ColorGamuts: decide whether values are coverage or relative gamut size #51.

    Needs a source check (no notes page)

    • Huion H610 and Kamvas RDS-160: the body is smaller than the active area.
    • 269 core fields are missing across the remaining tablets, mostly older Wacom models.

    Next: a source pass over the 99 notes-page tablets, comparing each record against its manufacturer spec page or manual (the MANUFACTURERPRODUCTINFO / MANUFACTURERUSERMANUAL links). The same pass can sort each gamut figure into coverage or area (#51) and record coatings (#56).


    Generated by Claude Code

  2. TheSevenPens commented on Oct 2, 2026

    @TheSevenPens
    Owner

    Conventions decided by Seven (2026-10-02)

    1. Color depth: Display.ColorBitDepth keeps the panel's native depth (6, 8 or 10). A new Display.ColorBitDepthFRC holds the depth the manufacturer claims with FRC, and is set only when they say FRC ("8-bit + FRC", "1.07B colors" on an 8-bit panel). The Specs row reads "8-bit (10-bit with FRC)" when both are set, and "10-bit" for a true 10-bit panel. Recheck the 20 tablets recorded as 10-bit today, since some are likely 8-bit + FRC.
    2. Buttons means programmable buttons only. Count multimedia keys in their own field, and scrollers in their own field.
    3. Depth ranges ("19~26.7 mm"): store a distinct min and max. If only one value is given, it is the max.
    4. Hover ranges: undecided. Count how many sources give a range first.
    5. A single accuracy figure with no center/corner split: store it as center accuracy.
    6. A built-in fold-out stand counts as Legs only, not IncludedStand.
    7. Report rate: store both wired and Bluetooth. If only one value is given, it is the wired one.

    Generated by Claude Code

  3. TheSevenPens commented on Oct 2, 2026

    @TheSevenPens
    Owner

    Seven's answers (2026-10-02 21:27 UTC)

    These map to the numbered questions Seven was asked:

    1. HS610: merge. Merge the "H610" record (huion.tablet.h610) into the existing huion.tablet.hs610, keeping its 12 buttons and 1 touch ring, delete the H610 record, and point the pen-compat entry for "H610" at HS610. Seven: the HS610 is discontinued.
    2. Intuos 1 ADB (GD-…-A): yes. Copy the digitizer specs from the -R/-U versions: 1024 levels, EMR, ±0.25 mm center accuracy, hover, report rate.
    3. UltraPad: yes. Use Wacom's 1997 figures:
      • 6×8 weight 862 g
      • 12×12 size 406 × 419 × 51 mm
      • 12×18 weight 3402 g
      • 18×25 active area 635 × 457.2 mm at 100 lines/mm
    4. Hover ranges: yes. On the two Magic Drawing Pads, store a min and a max like depth: 10 and 20 mm.
    5. Inspiroy 2 L group keys: yes, their own field. Seven: they are "switcher" keys, not assignable in the normal sense for shortcuts.
    6. Go live: yes. Merge the spec-audit-2 batch (audit fixes, conventions, and the answers above) into DrawTabData master and DrawingTabletDocs syncbranch.

    Generated by Claude Code

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions