2.9 KiB
Capture layout compatibility
- Flat legacy directories keep the existing filename requirements and one Run per directory. Nested files cannot satisfy root requirements. Multiple candidates for a required type block admission rather than selecting the first file.
- A direct
part[0-9]+child selects segmented layout. Each part is an independent unit, identified by workflow + parent prefix + part. Capture names are not restricted to FYLX or a date pattern. - Part video names must contain the actual Capture name, camera side and actual part name. Original
.mp4/.mov/.mkvand suffixed variants such as_silent_480p_wm.mp4are recognized. Multiple variants block intake as ambiguous. - Part PTS and IMU names must match the Capture and part exactly. Video-specific
<video-stem>_pts.csvtakes precedence over raw part PTS when present. Only the parent's two<capture>_calibration_camera.yaml/<capture>_calibration_imu.yamlfiles are shared. Audio and meta are optional. - Root sensor data plus part directories is a structural conflict. Missing/empty files block only their unit; missing shared calibration blocks all affected parts. Custom required patterns remain supported for flat layouts; for part layouts they add constraints within the selected unit, never permit cross-part matching.
- A directory reference records the parent
prefix, explicitobjectKeysand displaycaptureUnit. Both directory reading and normalization enforce the selection, including on retry. Missing selected files fail closed. Each part's fingerprint includes only its selected files and shared calibration/meta. - Existing admitted parent records retain their Run association and are not split/relaunched by scanning. Discarded or launching parents also prevent child admissions. No completion manifest is required; non-empty required files and the existing stability window still apply.
- Once a part has been admitted, the parent cannot later be admitted as a flat unit by moving/removing source files.
Data-quality boundary
Filename compatibility does not prove frame correspondence. In particular, a transcoded _silent_480p_wm.mp4 plus raw _part0001_pts.csv is recognized by intake but remains subject to the existing normalizer rejection when a matching transformed-video PTS/frame mapping is absent. This change must not invent timestamps or silently bypass that safety check.
Validation
Go tests cover flat/part grouping, independent identities/fingerprints, shared calibration, missing/empty/wrong-part files, duplicate videos, mixed layouts, historical-parent protection, Run binding/de-duplication and retry references. Python tests cover scope enforcement in both readers, parent calibration pairing and unchanged PTS safety.
Deploy worker, API and both directory-scan / Orbbec-normalization operator images together. Do not enable a new scanner with old operators that ignore objectKeys. No live deployment or business replay is performed by unit tests.