Config Schema Reference#
Preview: The config system and
PolicyRuntimeare planned APIs. The schemas below document the target design.
Config files use class_path and init_args to describe explicit component construction.
ComponentSpec#
Direct class mode:
class_path: package.module.ClassName
init_args:
key: value
Registry mode:
type: registered_name
key: value
The ComponentSpec fields are listed below.
Field |
Type |
Description |
|---|---|---|
|
string |
Fully qualified import path |
|
object |
Constructor keyword arguments |
|
string |
Registered short name |
extra fields |
any |
Flat constructor args for registry mode |
The core rules are straightforward.
A component spec must include either
class_pathortype.If both fields are present,
class_pathtakes precedence.Nested component specs are instantiated recursively.
RuntimeConfig#
runtime:
class_path: physicalai.runtime.PolicyRuntime
init_args:
fps: 30
robot:
class_path: physicalai.robot.so101.SO101
init_args:
port: /dev/ttyACM0
model:
class_path: physicalai.inference.InferenceModel
init_args:
export_dir: ./exports/act_policy
execution:
class_path: physicalai.runtime.SyncExecution
init_args:
mode: chunk
The most common runtime fields are listed below.
Field |
Type |
Description |
|---|---|---|
|
|
Runtime orchestrator |
|
number |
Control loop frequency |
|
|
Robot implementation |
|
|
Inference model |
|
|
Execution strategy |
|
mapping |
Optional camera components |
|
list |
Optional runtime callbacks |
InferenceConfig#
model:
class_path: physicalai.inference.InferenceModel
init_args:
export_dir: ./exports/act_policy
backend: openvino
device: CPU
The most common inference fields are listed below.
Field |
Type |
Description |
|---|---|---|
|
|
Inference model component |
|
string |
Exported package directory |
|
string |
Backend name or |
|
string |
Backend device or |
Config vs Manifest#
Schema |
Use |
|---|---|
Workflow config |
A workflow config describes a workflow before execution. |
Manifest |
A manifest describes an exported package after export. |