Description of the task
Currently, we use the full version of Raspian with every configuration of the robot. Despite not utilizing many of its features, such as it's graphical display output, we take on the compute overhead of the entire OS. This not only degrades the life expectancy of our memory (given the substantive overhead of complex operations), but also increases power draw, and latency in our OS. Thus, we should investigate alternative OS options, and headless mode for Raspian is in particular an easy option. This ticket involves validating our robot on a Pi using Raspberry Pi OS Lite, and documenting if it works and profiling what improvments (if any) we can observe.
Acceptance criteria
Blocked By
Description of the task
Currently, we use the full version of Raspian with every configuration of the robot. Despite not utilizing many of its features, such as it's graphical display output, we take on the compute overhead of the entire OS. This not only degrades the life expectancy of our memory (given the substantive overhead of complex operations), but also increases power draw, and latency in our OS. Thus, we should investigate alternative OS options, and headless mode for Raspian is in particular an easy option. This ticket involves validating our robot on a Pi using Raspberry Pi OS Lite, and documenting if it works and profiling what improvments (if any) we can observe.
Acceptance criteria
Blocked By