Back to corpus
research noteexperiment writeup candidatescore 32
LUME v2 twin-sensor checklist
_Comprehensive task list spanning hardware, CAD, software, calibration, testing, packaging, manuals, and ship-blocking dependencies. Ordered by unblock chain. Each item has owner, ETA, and verification criterion._
Full HTML reader
Read the full artifact
Extracted abstract or opening context
_Comprehensive task list spanning hardware, CAD, software, calibration, testing, packaging, manuals, and ship-blocking dependencies. Ordered by unblock chain. Each item has owner, ETA, and verification criterion._
- [ ] **Receive Bolt** (Apr 27, Prime) — Mohamed acknowledges arrival, opens box, verifies serial number, photographs port layout for cradle CAD reference. - [ ] **Receive K11** (next-day if ordered now) — Mohamed unboxes, plugs in, verifies BIOS boot, confirms Linux installable. ETA per K11 BOM memo. - [ ] **Capture Bolt STEP file** from `github.com/orbbec/OrbbecHardware`. Drop into `hardware/cad/references/orbbec-femto-bolt.stp`. Convert to STL via FreeCAD (FreeCAD → open .stp → export STL). Drop into `hardware/cad/references/orbbec-femto-bolt.stl`. Add `USE_REAL_BOLT=true` toggle in lume-config-bolt.scad. - [ ] **Caliper-measure Bolt** — verify the 140×39×30mm we're using. Reconcile with STEP. Update DIMENSIONAL-AUDIT.md confidence to ⭐. - [ ] **Caliper-measure K11** — verify 142.6×113×49.5mm. Reconcile. - [ ] **Caliper-measure Mega's Jetson hump** — verify the +25mm protrusion claim. - [ ] **Reconcile Mega axis labels** — physically measure Mac4's Mega and update FEMTO_W/D/H constants if they're swapped.
- [ ] **Run femto_intrinsics.py against Bolt** to capture intrinsics JSON. Save as `software/demo/femto_intrinsics_bolt.json`. Compare against Mega's intrinsics — should be similar since same sensor silicon. - [ ] **Test Bolt with existing pointcloud_pub.py** — invoke `python3 pointcloud_pub.py --raw-depth --intrinsics-json femto_intrinsics_bolt.json --host [ip] --port 9700` and verify LUMD packets flow at expected 6720/sec rate. - [ ] **Test Bolt over USB-C to K11** (when K11 arrives) — same publisher command from K11 side instead of Mac4. Verify USB4 port is fast enough for 1024² depth at 30fps. - [ ] **Verify Bolt depth quality matches Mega** — capture same scene with both, compare depth maps via `lume_packet_inspector.py --hex` for byte comparison. Should be functionally identical given same Sony IMX556.
- [ ] **Add lume-config-bolt.scad** with overrides: LUME_DEPTH=60, FEMTO_W=140, FEMTO_D=39, FEMTO_H=30, FEMTO_MOUNT_PITCH_X=TBD, FEMTO_MOUNT_PITCH_Z=TBD. Inherit everything else from lume-config.scad via include. - [ ] **Refactor lume-shell.scad** to parameterize against current config rather than implicitly using the global lume-config.scad. Add config-include hook so lume-shell-bolt.scad can drive it. - [ ] **Generate lume-shell-bolt.scad** entrypoint that includes both configs and renders the Bolt-config bar. - [ ] **Rebuild Bolt cradle module** in lume-shell.scad to handle the new camera dimensions. Bolt has different mount pattern; needs new bolt hole positions in the cradle plate. - [ ] **Re-export 4 Bolt shell halves** — s
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.