AI4Manufacturing/DD1_2

Roles

Roles: canon repo — annot is the source label, kept machine-parseable as the gold for verification and reward parsing; there is no reasoning column and this repo is not itself a training view. Derived repos (-annotated, -grounding, -region, -mcq) each state their own regime on their own card. Geometry for every record lives in metadata.geometry (below).

DD1 PB VQA Grounding

Answer-only VQA-style grounding data derived deterministically from the PB portion of DD1_cleaned_grounding.

Schema

field	type	meaning
query	string	one of 34 deterministic LPBF PB grounding prompts
image	Image	original 1280×1024 JPEG bytes; never cropped
annot	string	JSON list [{"bbox_xywh":[x,y,w,h]}], or []
reasoning	null	answer-only dataset
cate	string	B
task	string	T-B1
metadata	string	JSON provenance, hashes, boxes and disclosures

Coordinates use native pixels with top-left origin. Width and height are xmax-xmin and ymax-ymin.

Counts

• Records: 2637
• Positive images: 1529
• Good/negative images: 1108
• Total boxes: 5000
• Query variants: 34
• Split: train only

Load

from datasets import load_dataset
ds = load_dataset(
    "parquet",
    data_files={"train": "data/train-00000-of-00001.parquet"},
)

annot is the direct SFT answer. reasoning is null on every row.

Reproduce

python3 -m pip install -r requirements.txt
python3 build_dd1_pb_vqa.py \
  --source /path/to/DD1_cleaned_grounding \
  --output /path/to/DD1_PB_VQA_grounding

Disclosure

The source uses the generic class label defects without a subtype taxonomy. Good means no author-annotated PB defect under the source labeling rule; it does not guarantee absence of every possible manufacturing defect.

Geometry (metadata.geometry)

Every record carries a geometry block inside the existing metadata JSON string, so that its gold can be re-derived at any render size. No schema column changed; existing loaders are unaffected.

Coordinates are native pixels of the image in that record (coords_frame: "record_image"). scale is 1.0 throughout — this repo publishes at source resolution, nothing was downscaled at publish time.

"geometry": {
  "image_wh":  [W, H],        // dims of the image in THIS record
  "source_wh": [W, H],        // dims of the original source image
  "scale": 1.0,               // image_wh / source_wh; < 1.0 would disclose a publish-time downscale
  "n_instances": 2,
  "instances": [
    { "instance_id": 1, "bbox_xywh": [x, y, w, h], "min_side_px": 65, "class": null }
  ],
  "n_dropped_subminimum": 0,  // components removed by the filters below
  "union_box_fallback": false,// true => boxes are per-class unions, NOT real instances
  "conventions": { ... }      // see table
}

instances is present even when empty. [] means the record genuinely has no defects; an absent block would mean geometry could not be recovered. Those are different states and are never conflated.

Conventions used to derive it

There is no universal definition of "one defect instance" — it depends on the mask the source shipped. This repo's is stated, not implied:

field	value
algorithm	source_annotation
binarisation	n/a
connectivity	4
merge	none
min_area_px	0
max_instances	None
artifact	fine
fill_floor	None
legibility_floor_px	None
min_side_floor_px	None
spec_sha	5e7f4314c8441019

Provenance and verification

records	2,637
carrying a geometry block	2,637 / 2,637
instances per record	0: 1,108, 1: 346, 2: 111, 3: 572, 4: 216, 5+: 284
total instances	5,000
image dimensions	1280×1024 (2,637)
scale values present	[1.0]

Computed from this repo's own masks and verified against this repo's own published answers before it was written — a recomputation that disagreed with the shipped gold would have aborted the update rather than overwritten it.

⚠ The 16px floor applies at the RENDER, not at native

min_side_px is in native pixels. The model does not see native: Qwen2-VL caps by megapixels AND snaps each dimension to a multiple of 28. So min_side_px >= 16 is the floor tested in the wrong frame. Measured on this repo:

native → rendered (qwen2_vl @ 2.36MP)	1280×1024 → 1288×1036
shipped boxes	5,000
legible at that render (>=16px there)	4,114 (82.3%)

⚠ An earlier version of this section reported the inverse — boxes clearing 16px at native and failing at the render — and that number was misleading. It is frame-relative: publishing at a larger native size lets more boxes clear 16 in the published frame, so more can "fail", which penalises exactly the choice that helps. Measured on 179: publishing native (3024) means a box needs >=32px native to be legible at the render and 86.7% qualify; the previous 1024 publish needed >=47px native and only 69.5% qualified. The native republish improved rendered legibility by 17 points while the old metric scored it as 12.5% "broken". The figure above is the comparable one.

Nothing in the data is frame-dependent — geometry is native and complete. Use forge_model/common/adapt_engine.py, which applies the floor at whatever size the consumer renders.

Using it

Coordinates only stay correct if they are rescaled with the image. A patch-based VLM does not render at native size: Qwen2-VL's processor snaps both dimensions to a multiple of 28, so this repo's 1280×1024 is rendered 1288×1036 and native-pixel boxes are then wrong by a few pixels. forge_model/common/adapt_engine.py regenerates coordinates for a target render size, re-derives counts, and drops records whose gold no longer holds there.