A two-camera robot whose captures are driven by
BB.Camera.FFmpeg.Test.StubBackend.
Everything but the bytes is real: the real driver, the real hub, the real
framer and the real capture bounds. Only the thing that would have been
rpicam-vid is replaced, so a test can decide exactly what each camera
produces and when.
:eye is chosen by index, and its width comes from a parameter so a test
can reconfigure it the way a robot actually does. :right is chosen by
libcamera id, which the driver resolves by running fake_rpicam_vid --list-cameras - a script replaying a real Pi 5's listing. :ghost names
an id that listing doesn't have.
The stub reports to whatever process is registered as
:bb_camera_libcamera_stub_observer, because the DSL is compiled long
before any test process exists.
Summary
Functions
Returns default parameter values.
Returns the parameter schema for validation.
Returns a child specification for starting this robot under a supervisor.
Returns the optimised robot representation.
Starts the robot's supervision tree.
Functions
Returns default parameter values.
Returns a list of {path, value} tuples for parameters that have defaults.
Returns the parameter schema for validation.
The schema is a list of {path, opts} tuples where opts is a keyword
list compatible with Spark.Options.
@spec child_spec(Keyword.t()) :: Supervisor.child_spec()
Returns a child specification for starting this robot under a supervisor.
@spec robot() :: BB.Robot.t()
Returns the optimised robot representation.
This struct is built at compile-time from the DSL definition and contains:
- All physical values converted to SI base units (floats)
- Flat maps for O(1) lookup of links, joints, sensors, and actuators
- Pre-computed topology metadata for efficient traversal
Examples
robot = Elixir.BB.Camera.Libcamera.Test.StubBot.robot()
{:ok, link} = BB.Robot.get_link(robot, :base_link)
{:ok, joint} = BB.Robot.get_joint(robot, :shoulder)
@spec start_link(Keyword.t()) :: Supervisor.on_start()
Starts the robot's supervision tree.
Options
All options are passed through to sensor and actuator child processes.