Runtime Context¶
Context is the most important object in armnet-runtime. Every
@main-decorated runtime function receives one:
from armnet_runtime import Context, main
@main
def run(ctx: Context) -> dict:
ctx.report_progress("starting")
return {"job_id": ctx.job_id}
Context Fields¶
| Field | Type | Description |
|---|---|---|
job_id |
str |
Platform job ID for the current execution. |
embodiment |
str |
Robot embodiment requested by the job, e.g. lerobot/so-101 or lerobot/arx5. |
task |
str |
Task routed to the cell, e.g. assemble_block_tower. |
args |
dict[str, Any] |
JSON arguments supplied by execute(..., args={...}). |
cell |
Cell |
Handle for robot-cell services such as reset, completion, robot port, calibration, and language instruction. |
camera_configs |
dict[str, Any] |
LeRobot camera configs injected by the cell from robot_cell.json. |
cache_home |
Path | None |
Per-user cache directory. HF_HOME points inside this directory. Cache data may be reused but is not a durable API. |
volume |
Volume |
Per-user persistent volume mount. Use this for checkpoints, artifacts, and files that should survive across runs. |
secrets |
dict[str, str] |
Secret values injected into the job, keyed by environment variable name. Values are also available as process env vars. |
timeout_seconds |
int | None |
Wall-clock timeout requested for the container. |
Methods¶
ctx.report_progress(message)¶
Emits a progress line to stdout with a armnet marker. The cell streams this line back to the client alongside normal container logs.
ctx.report_progress("connected to robot")
ctx.log_rerun_data(observation=None, action=None, compress_images=True)¶
Streams observation/action data to a Rerun viewer running on
the client. Scalars are logged as Rerun scalars, image-like arrays as images,
and other arrays as per-element scalars; keys are namespaced with
observation. / action. when not already.
The cell container has no viewer, so this serializes a protobuf packet, the cell
republishes it on logs.<job_id>.rerun, and the client's orchestrate script
replays it into the viewer it started with rr.init(...). Images are
JPEG-compressed by default to keep the NATS stream light (compress_images=False
sends raw RGB).
obs = robot.get_observation()
action = policy.select_action(obs)
robot.send_action(action)
ctx.log_rerun_data(observation=obs, action=action)
On the client side, start a viewer and opt into streaming:
from armnet_client import execute, init_rerun
init_rerun("my-eval", spawn=True) # requires the `viz` extra
execute(image=img, embodiment=..., task=..., args={"use_rerun": True}, use_rerun=True)
Cell¶
ctx.cell describes the physical robot cell the job is running on.
| Field / Method | Type | Description |
|---|---|---|
robot_port |
str | None |
Value to pass into LeRobot robot configs. In remote containers this is a connector endpoint, not the host serial/device path. |
robot_id |
str | None |
Stable robot ID used by LeRobot calibration lookup. |
calibration_dir |
Path | None |
Calibration directory visible inside the container. |
calibration_file_path |
Path | None |
Exact calibration file path visible inside the container. |
arms |
dict[str, RuntimeArm] |
Named arms for a multi-arm cell, keyed by names such as left and right. Empty for single-arm cells. |
is_bimanual |
bool |
True when the cell exposes both left and right arms. |
arm(name) |
method | Return one named RuntimeArm, including its connector endpoint and calibration path. |
prepare_bimanual_calibration_dir() |
method | Copy per-arm calibration files into LeRobot's expected <robot_id>_left.json / <robot_id>_right.json layout and return a BimanualCalibrationLayout containing robot_id and calibration_dir. |
language_instruction |
str | None |
Natural-language instruction for the cell's assigned task (set from the FMS/database, forwarded to the cell when it starts). |
reset(message=None) |
method | Blocks until the operator confirms the workspace has been reset. |
is_complete(block=False) |
method | Returns a CompletionStatus(complete, success). A human operator's success/fail verdict (reported from the FMS during a rollout) wins and ends the episode immediately; otherwise the automated completion monitor is consulted (where success == complete). bool(status) is status.complete, so if ctx.cell.is_complete(): still works. |
rollout_begin(index=None, total=None, outcome_controls=True) / rollout_end() |
method | Announce the start/end of a rollout/episode in the job's loop. Pass index (1-based) and total so the FMS shows loop progress ("rollout N / M") for evals and data collection. With outcome_controls=True (default, for policy evals) the FMS also shows operator Success/Fail buttons; hitting one ends the rollout with that verdict (and triggers a workspace reset) without stopping the job. Pass outcome_controls=False for progress-only loops such as teleop data collection. Best-effort signalling. |
Example:
cfg = SO101FollowerConfig(
port=ctx.cell.robot_port,
id=ctx.cell.robot_id,
calibration_dir=ctx.cell.calibration_dir,
cameras=ctx.camera_configs,
)
robot = SO101Follower(cfg)
robot.connect(calibrate=False)
ctx.cell.reset("Reset the workspace, then press Enter.")
For bimanual SO-101 cells, use the named arms and LeRobot's BiSOFollower:
from lerobot.robots.bi_so_follower import BiSOFollower, BiSOFollowerConfig
from lerobot.robots.so_follower import SO101FollowerConfig
layout = ctx.cell.prepare_bimanual_calibration_dir()
robot = BiSOFollower(
BiSOFollowerConfig(
id=layout.robot_id,
calibration_dir=layout.calibration_dir,
left_arm_config=SO101FollowerConfig(port=ctx.cell.arm("left").robot_port),
right_arm_config=SO101FollowerConfig(port=ctx.cell.arm("right").robot_port),
)
)
Volume¶
ctx.volume gives runtime code access to the user volume mounted into the
container.
checkpoint_dir = ctx.volume.path("openpi/checkpoints/my-checkpoint")
config_text = ctx.volume.read_text("configs/eval.json")
ctx.volume.write_text("outputs/status.txt", "done")
Volume paths must be relative and cannot contain ...
Context
dataclass
¶
Everything a @main-decorated function needs from the platform.
Source code in runtime/src/armnet_runtime/context.py
652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 | |
report_progress
¶
report_progress(message: str) -> None
Surface a progress message back to the platform.
M0.5: prints to stdout with a discoverable marker so the cell's captured stdout shows progress in order with other prints. M1+ will also publish a NATS message so the orchestrator can stream progress back to the client without waiting for the job to terminate.
Source code in runtime/src/armnet_runtime/context.py
670 671 672 673 674 675 676 677 678 679 680 681 682 683 | |
log_rerun_data
¶
log_rerun_data(observation: dict[str, Any] | None = None, action: dict[str, Any] | None = None, *, compress_images: bool = True, jpeg_quality: int = 75) -> None
Stream observation/action data to a Rerun viewer on the client.
Mirrors LeRobot's log_rerun_data: scalars are logged as Rerun
scalars, image-like arrays as images, and other arrays as per-element
scalars. Keys are namespaced with observation. / action. when
not already.
Unlike the LeRobot helper, this does not call rr.log in-process
(the cell container has no viewer). Instead it serializes a protobuf
packet and emits it on stdout behind a marker; the cell republishes it
on logs.<job_id>.rerun and the client's orchestrate script replays
it into the viewer it started with rr.init(...).
Images are JPEG-compressed by default to keep the NATS stream light;
set compress_images=False to send raw RGB. opencv is required for
compression and numpy for any array handling; both are imported lazily.
Non-blocking: the snapshot is handed to a background worker thread that
does the encoding and stdout write, so the calling control loop never
stalls on visualization. The worker's queue is bounded and drops the
oldest pending frame under backpressure (tune with
ARMNET_RERUN_QUEUE_MAXSIZE), so a slow consumer sheds frames
rather than slowing the robot loop.
Source code in runtime/src/armnet_runtime/context.py
694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 | |
Cell
dataclass
¶
Handle to the physical cell the user code is running on.
M0.5 stub: there is no real cell yet, so robot_port is always None
and :meth:reset is a no-op. The shape is fixed now so the spec
example compiles end-to-end and so M2/M3 can fill in the
implementation without touching customer-facing imports.
Source code in runtime/src/armnet_runtime/context.py
134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 | |
arm
¶
arm(name: str) -> RuntimeArm
Source code in runtime/src/armnet_runtime/context.py
194 195 196 197 198 | |
prepare_bimanual_calibration_dir
¶
prepare_bimanual_calibration_dir() -> BimanualCalibrationLayout
Create a temp calibration dir using LeRobot's <base>_<arm>.json names.
Each arm's source calibration is resolved (in order) from its own
calibration_file_path, its own calibration_dir keyed by the arm's
robot_id, or—when the arm declares neither—the cell-level
calibration_dir keyed by the arm's robot_id (<robot_id>.json).
This mirrors how the cell's per-arm health check resolves calibration
(arm.calibration_dir or cell.calibration_dir), so a config that only
sets a top-level calibration_dir (per-arm robot_id only) works.
Source code in runtime/src/armnet_runtime/context.py
200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 | |
reset
¶
reset() -> None
Return the robot to rest, then block until the operator confirms.
Two concerns, two endpoints:
- Returning the arm to its rest position is a low-level bus operation,
so it is sent to the robot connector (
robot_port), which may be a headless edge device. - Operator confirmation is a human-in-the-loop concern, so it is sent
to the
operator_call_endpointserved by thearmnet-cellprocess, whose stdin is the operator's terminal.
The operator-facing prompt is owned by the cell, not by job code: job code only signals that a reset point has been reached.
Source code in runtime/src/armnet_runtime/context.py
236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 | |
is_complete
¶
is_complete(*, block: bool = False) -> CompletionStatus
Return whether the current episode is complete, and its success.
Returns a :class:CompletionStatus (complete, success):
- A human-reported outcome (an operator hitting success/fail in the
FMS during a live rollout) takes precedence and ends the episode
immediately, with
successset to the operator's choice. This is how an operator stops a dangerous rollout without stopping the job. - Otherwise the cell's automated completion monitor is consulted; a
task scored complete is reported as a success (
success == complete). Passblock=Truefor a final episode check that waits for the cell to score the latest cached frames before returning.
bool(status) is status.complete for backwards compatibility.
Source code in runtime/src/armnet_runtime/context.py
277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 | |
rollout_begin
¶
rollout_begin(*, index: Optional[int] = None, total: Optional[int] = None, outcome_controls: bool = True) -> None
Tell the platform a rollout/episode in this job's loop has started.
The cell publishes this to the FMS, which shows the loop progress
("rollout N / M") for the live job. Pass index (1-based) and, when
known, total so operators see how far along the loop is.
outcome_controls controls whether the FMS also shows operator
success/fail buttons: keep the default True for policy evals; pass
False for progress-only loops such as teleop data collection, where
a human verdict doesn't apply. Best-effort: a failed notification never
breaks the rollout. Pair with :meth:rollout_end.
Source code in runtime/src/armnet_runtime/context.py
349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 | |
rollout_end
¶
rollout_end() -> None
Tell the platform the current rollout has ended (hides FMS buttons).
Source code in runtime/src/armnet_runtime/context.py
375 376 377 | |
Volume
dataclass
¶
User volume mounted into the runtime container.
Source code in runtime/src/armnet_runtime/context.py
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 | |
path
¶
path(relative_path: str | Path) -> Path
Source code in runtime/src/armnet_runtime/context.py
87 88 89 90 91 92 93 | |
read_bytes
¶
read_bytes(relative_path: str | Path) -> bytes
Source code in runtime/src/armnet_runtime/context.py
95 96 | |
read_text
¶
read_text(relative_path: str | Path) -> str
Source code in runtime/src/armnet_runtime/context.py
98 99 | |
write_bytes
¶
write_bytes(relative_path: str | Path, data: bytes) -> Path
Source code in runtime/src/armnet_runtime/context.py
101 102 103 104 105 | |
write_text
¶
write_text(relative_path: str | Path, data: str) -> Path
Source code in runtime/src/armnet_runtime/context.py
107 108 109 110 111 | |