liveBook · Manning

Abstraction

As explained in Robotics for Programmers

An abstraction is a simplified interface or representation that hides irrelevant implementation details.

In robotics, an abstraction gives higher-level code a meaningful interface while hiding raw sensor and actuator details. Instead of interpreting a switch state or voltage throughout movement logic, code can ask whether a collision occurred or whether a computer is active. section 3.2.1

From raw brightness to robot meaning

get_brightness() converts an analog voltage into candela, while is_computer_active() compares that value with an activity threshold. Code elsewhere uses the meaningful condition instead of sensor-specific details.

How Robotics for Programmers covers it

How deep it goes
Shows encapsulation through sensor predicates, subsystems, conversions, and thresholding, without developing larger layered robot architectures.
Examples
Uses collision switches, analog distance conversion, coffee supply thresholds, and computer-activity detection.
What it assumes
Assumes basic robot inputs and functions while demonstrating encapsulation from raw digital and analog readings.
What you can do after
Apply it by replacing raw input checks with meaningful sensor interfaces and domain-level predicates.
How it connects
Connects encapsulation with sensor data processing, collision detection, analog inputs, and planning.

Also explained in

Compare how 24 books explain abstraction →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Robotics for Programmers. The section links point to the parts of the book it draws on.