Data Types

Data types used in the tasks are defined in the library redcp, which contains support wrappers for data structures commonly used in robotics. The individual data types allow for standardizing the interfaces between the functional parts of the robot software architecture. The implementation of the library is inspired by the ROS middleware used in robotics to manage the software architecture of the robots. While the ROS messages are only data wrappers, our implementation features several simplifications, and some classes include additional code to simplify work with them.

The data types used in the course tasks are inherited from the Message class and are as follows.

  1. Header
  2. Vector3
  3. Quaternion
  4. Pose
  5. Odometry
  6. Twist
  7. Path
  8. LaserScan
  9. OccupancyGrid
  10. NavGraph

The structure of the individual classes and the description of their methods follows.


The general message header contains information common for most data (message) types.

Attributes


Vector3

Representation of 3D vectors with $x$, $y$, $z$ component.

Attributes


Quaternion

Representation of 3D orientation using unit quaternion. There are multiple ways to represent the rotations in robotics, with the rotation matrices and quaternions being superior to Euler angles with their commonly used variant Tait–Bryan angles. The Euler angles represent the robot orientation in 3D using rotations around the principal axes of the robot. In particular, the original Euler angles are prescribed by one of the following orders of rotation ($zxz$, $xyx$, $yzy$, $zyz$, $xzx$, $yxy$) with the more common representation using the Tait–Bryan angles variant prescribed by one of the following orders of rotation ($xyz$, $yzx$, $zxy$, $xzy$, $zyx$, $yxz$) commonly referred to as yaw (rotation around $z$ axis), pitch (rotation around $y$ axis), and roll (rotation around $x$ axis) of the robot, similar to the following figure (courtesy of novatel.com).

There are two principal problems in using Euler (Tait–Bryan) angles. First is the missing standardization of rotation order, which leaves us with twelve possible sequences of rotations. Second, the Gimball-lock effect, which is a loss of Degree of Freedom that occurs when two axes are driven into a parallel configuration by the sequence of the rotations. Hence, representation of the orientation using quaternions and rotation matrices is considered a better option.

Attributes

Methods


Pose

Class representing robot pose in free space in the form of $x$, $y$, $z$ position vector, and orientation quaternion.

Attributes

Methods


Path

Class representing the robot path in free space as a list of poses.

Attributes

Methods


Odometry

Class representing robot odometry as a timestamped pose in the given reference frame.

Attributes


Twist

Class representing velocity in free space broken into linear and angular components.

Attributes


LaserScan

Class for representing a single line scan from a planar laser scanner.

Attributes

Methods


OccupancyGrid

Class representing occupancy grid map.

Attributes

Methods


Class representing the navigation graph $\mathcal{G}=(V, E)$, where $V$ is a set of vertices and $E$ is a set of edges.

Attributes

Methods