eclise

Shared research infrastructure: one eclise wheel under the PEP 420 namespace eclise.*. The folder taxonomy is organizational only — imports are always flat eclise.<name>. Heavy stacks live in pixi environments, not in wheel metadata.

Extras (the published wheel)

eclise.octo / smolvla / libero / phyworld / openvid / pi0 / launch ship as inert source in the same wheel. Running a server or generator needs the matching pixi environment (or python -m eclise.launch).

models/vision/ is deliberately absent: a vision-model contract will be created only once it has at least two real consumers.

Pixi environments (from a checkout)

Installing

Client-side (numpy-1.x-safe eclise.vla only — no torch/jax):

pip install "eclise[octo,libero]"
python -m eclise.launch start octo --setup

--setup clones this repo at eclise-v<wheel version> (unless ECLISE_ROOT already points at a checkout), installs pixi if needed, and runs pixi install -e <env>. start returns a host/port; the caller wires WebsocketPolicyClient / WebsocketEnvClient.

From a checkout:

pixi install -e dev
pixi run -e dev test
pixi run -e libero setup
pixi run -e libero serve --port 9000

Developing

pixi run -e dev test
pixi run -e libero serve
pixi run -e phyworld generate --family collision --grid in_dist_l0 --experiment smoke --limit 32

Editable extras without pixi: pip install -e ".[dev]". Releases are tagged eclise-v0.1.0.

Design rules

• One distribution, environments at the pixi boundary. Incompatible stacks (JAX vs torch, numpy 1.x vs 2.x) do not share an environment. Wheel extras stay light; pixi features own the heavy pins.
• Imports are flat, folders carry taxonomy. Moving a package between folders is never a breaking change for consumers.
• eclise.clips and eclise.vla are contracts. Writers and readers may live in different repos/envs; document schema changes in CHANGELOG.md. eclise[vla] must remain numpy 1.x-compatible.

Package archetypes

Every package is one of three kinds. New packages pick one and follow its rules rather than inventing a fourth layout.

Library extra — published wheel, installed into a consumer's env, no server. utils, datasets, clips, vla.

Interactive socket service — pixi env isolates an incompatible stack behind an eclise.vla websocket. octo, smolvla, pi0, libero.

• Env: pixi install -e <name> (and pixi run -e <name> setup when the feature defines a setup task).
• Server logic lives in the package as eclise.<name>.serve (pi0 wraps upstream openpi instead).
• Launch: python -m eclise.launch start <name> → pixi run -e <env> serve.

Batch producer — pixi env; decoupled via the on-disk eclise.clips shard contract (no socket). phyworld, openvid.

• Env: pixi install -e <name> + pixi run -e <name> setup (scratch data/ / outputs/ symlinks).
• Job entrypoint: scripts/<verb>.py (+ .sbatch via pixi run -e <env>).
• Producer verify: scripts/verify_shards.py.