[good-first-issue] bridge-python: long-running bridge or multi-stream inject · bridge 상시 데몬 또는 multi-stream inject
Labels: feature, help wanted, area:bridge-python, area:runtime, priority:medium
Related: bridge-python/ROBOTICS.md · Not in scope · 19-physical-ai-sim-real-track.md
Context · 배경
Current demos (demo_spider_sim.py, demo_pet.py, …) spawn subprocess cell run per sample. That is fine for CI and learning, but real robots need either:
현재 데모는 샘플마다 subprocess cell run 을 호출합니다. CI·학습에는 적합하나, 실제 로봇에는 다음 중 하나가 필요합니다:
- Long-running bridge — one runtime session, periodic inject
상시 bridge — 단일 런타임 세션, 주기 inject
- Multi-stream parallel inject — e.g. vision + IMU in one organism session
multi-stream parallel inject — 예: vision + IMU 동시 inject
cell run --stream today batches one stream name per session (stream-run.ts).
Goal · 목표
Design + minimal PoC for one of (maintainer picks scope in Discussion):
Design + minimal PoC (Discussion에서 범위 선택):
| Option |
Deliverable |
| A |
demo_* --daemon loop: in-process CellRuntime or persistent Node worker · in-process 런타임 |
| B |
run_cell_multi_stream() — two stream payloads, one session API · dual-stream API |
| C |
Document won’t fix in v0.1 with recommended external orchestration (ROS2 node, etc.) · v0.1 won’t fix 문서 |
Tasks · 작업 (Option A example)
Tasks · 작업 (Option B example)
Definition of done · 완료 기준
- Discussion link in PR describing chosen option (A/B/C)
PR에 선택한 옵션(A/B/C) Discussion 링크
npm test + bridge smoke tests pass
npm test + bridge smoke 통과
ROBOTICS.md “Not in scope” section updated
ROBOTICS.md 미구현 섹션 갱신
References · 참고
typescript/stream-run.ts, bridge-python/cell_bridge/runner.py
rfcs/RFC-0001-stream-membrane-physical-sla.md
[good-first-issue] bridge-python: long-running bridge or multi-stream inject · bridge 상시 데몬 또는 multi-stream inject
Labels:
feature,help wanted,area:bridge-python,area:runtime,priority:mediumRelated:
bridge-python/ROBOTICS.md· Not in scope ·19-physical-ai-sim-real-track.mdContext · 배경
Current demos (
demo_spider_sim.py,demo_pet.py, …) spawn subprocesscell runper sample. That is fine for CI and learning, but real robots need either:현재 데모는 샘플마다 subprocess
cell run을 호출합니다. CI·학습에는 적합하나, 실제 로봇에는 다음 중 하나가 필요합니다:상시 bridge — 단일 런타임 세션, 주기 inject
multi-stream parallel inject — 예: vision + IMU 동시 inject
cell run --streamtoday batches one stream name per session (stream-run.ts).Goal · 목표
Design + minimal PoC for one of (maintainer picks scope in Discussion):
Design + minimal PoC (Discussion에서 범위 선택):
demo_* --daemonloop: in-processCellRuntimeor persistent Node worker · in-process 런타임run_cell_multi_stream()— two stream payloads, one session API · dual-stream APITasks · 작업 (Option A example)
--daemon --interval-ms 33ondemo_spider_sim.py· 데몬 플래그ROBOTICS.mdarchitecture diagram · 문서Tasks · 작업 (Option B example)
stream-run.ts/runner.pyfor{ VisionStream: [...], ImuStream: [...] }· dual stream.cellchange — separate RFC) · parallel sensingDefinition of done · 완료 기준
PR에 선택한 옵션(A/B/C) Discussion 링크
npm test+ bridge smoke tests passnpm test+ bridge smoke 통과ROBOTICS.md“Not in scope” section updatedROBOTICS.md미구현 섹션 갱신References · 참고
typescript/stream-run.ts,bridge-python/cell_bridge/runner.pyrfcs/RFC-0001-stream-membrane-physical-sla.md