Skip to content

mcap_to_lance: port the vendor converter onto the current Lance stack - #757

Draft
SaveAanchal wants to merge 1 commit into
aanchal/lance-stack-fixesfrom
aanchal/mcap-lance-port
Draft

SaveAanchal wants to merge 1 commit into
aanchal/lance-stack-fixesfrom
aanchal/mcap-lance-port

Conversation

@SaveAanchal

Copy link
Copy Markdown
Contributor

Replaces #719, which had drifted from the stack. Vendor MCAP episodes stage per lab under mcap-<lab>/, with a task list per delivery and the Aria focal chosen by rig name.

Tested: synthetic episodes on a local root, MANO off.
Not tested: real MCAP deliveries, MANO on this path, or training on its output. test_mcap_to_lance_aria.py has not been run. Not ready for vendors.

🤖 Generated with Claude Code

Brings the #719 converter over from origin/aanchal/ingest and matches it to the
current MCAP spec and committer:

- Episode info uses the snake_case keys and annotation_source; `site` is gone, a
  label with no source is credited to the episode's lab.
- Recordings carry end_effector. Aria's focal is chosen by rig_name, since lab now
  means who collected the data.
- A delivery is steps.parquet, MP4s and meta.json, staged with commit.stage, under
  <staging>/mcap-<lab>/<vendor id>/ because vendor ids are only unique within a lab.
  A lab that can't name a folder is rejected.
- Committer: Delivery.tasks is a list (a /task topic can hold several); meta-based
  loading takes an optional `tasks` list; `--source mcap-<lab>`; a delivery's
  annotation_type is kept. Aria, EVA and zarr deliveries load as before.
- A re-export now removes only the lab's own labels, not ones credited to another
  annotation_source.

Fixtures gain #719's options (vendor_recording_id now follows episode_id). SPEC.md
documents the wrist frame, video outputs and staging path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant