Skip to content

feat: create roboharness/showcase repository #139

Description

@MiaoDX

Context

GR00T N1.6, Pi0, LeRobot, SONIC etc. need to demonstrate roboharness integration, but embedding them in the core repo would bloat it and explode dependencies. Redefines #91.

Priority: Do now.

Scope

1. Org setup

  • Create .github repo in roboharness org with profile/README.md (org landing page)

2. Showcase repo

  • Create roboharness/showcase repo
  • Initialize skeleton: README + directory structure
roboharness/showcase/
├── README.md
├── groot-n16/
├── pi0-libero/
├── lerobot-g1/
├── sonic-locomotion/
├── capx-comparison/
└── .github/workflows/showcase-ci.yml

3. First showcase

  • Extract examples/lerobot_g1_native.py as a standalone runnable showcase
  • Each showcase directory: README.md, requirements.txt, run.sh, main script

4. CI

  • GitHub Actions matrix — one independent job per showcase

Key design decisions

  • No git submodules — use requirements.txt + runtime pip install
  • Each showcase is self-containedcd showcase/groot-n16 && pip install -r requirements.txt && python groot_visual_test.py
  • roboharness is a pip dependency, not a submodule — always uses PyPI release
  • CI matrix — one failing showcase doesn't block others

Exit criteria

Showcase repo has at least 3 runnable showcases (GR00T, Pi0, LeRobot), each with CI.

References

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions