Skip to content

v0.1.2 alpha: recorded-camera timing and corpus compatibility

Pre-release
Pre-release

Choose a tag to compare

@gagandeepreehal gagandeepreehal released this 24 Oct 20:13
7f9d906

Camera exports now use the recorded-camera timestamp for every INDUS-AD recording, matching the original mz-datagen selection convention. Main GNSS retains its sensor timestamp. Untimed quality-flagged GNSS messages define excluded portions; usable portions remain eligible rather than rejecting the entire recording.

  • Preserve consistent nonzero GNSS origins, signed source offsets and missing diagnostics on quality-flagged messages without inventing data.
  • Keep exact source annotation identities while mapping verified source frames to recorded-camera export times.
  • Document timing, trimming, troubleshooting, manual access review and reproducible source compatibility results.

Validation: 1,039 tests, static analysis and offline export checks on Linux and macOS. Five representative real six-camera builds on macOS/Python 3.12 passed SDK loading, official nuScenes loading, all output-image decoding and CLI validation, yielding 229 samples and 1,374 images. Release evidence records the tested source revision and wheel hash.

This is an alpha prerelease. Metadata compatibility does not establish that every video has been decoded or that every recording yields an eligible scene. Production builds were tested with publisher credentials; no approved non-owner account was available for an access test. Hardware synchronization, physical calibration accuracy and privacy accuracy are not established by these software checks.

Python 3.12 is required. Dataset access is manually reviewed with no fixed turnaround. The software remains under PolyForm Noncommercial; the dataset license is unchanged. DOI registration remains on hold.