micro-ROS rolling Library auto-update 02-06-2022 06:14 (#553)

Co-authored-by: pablogs9 <[email protected]>

libmicroros/include/actionlib_msgs/msg/detail/goal_status__struct.h

@@ -38,7 +38,7 @@ enum
 /// Constant 'PREEMPTED'.
 /**
   * The goal received a cancel request after it started executing
-  * and has since completed its execution (Terminal State).
+  *   and has since completed its execution (Terminal State).
  */
 enum
 {
@@ -68,7 +68,7 @@ enum
 /// Constant 'REJECTED'.
 /**
   * The goal was rejected by the action server without being processed,
-  * because the goal was unattainable or invalid (Terminal State).
+  *    because the goal was unattainable or invalid (Terminal State).
  */
 enum
 {
@@ -88,7 +88,7 @@ enum
 /// Constant 'RECALLING'.
 /**
   * The goal received a cancel request before it started executing, but
-  *    the action server has not yet confirmed that the goal is canceled.
+  * the action server has not yet confirmed that the goal is canceled.
  */
 enum
 {
@@ -98,7 +98,7 @@ enum
 /// Constant 'RECALLED'.
 /**
   * The goal received a cancel request before it started executing
-  * and was successfully cancelled (Terminal State).
+  *    and was successfully cancelled (Terminal State).
  */
 enum
 {

libmicroros/include/control_msgs/action/detail/follow_joint_trajectory__struct.h

@@ -124,9 +124,9 @@ typedef struct control_msgs__action__FollowJointTrajectory_Result
   /// - INVALID_GOAL: The reason for the invalid goal (e.g., the requested
   /// trajectory is in the past).
   /// - INVALID_JOINTS: The mismatch between the expected controller joints
-  ///   and those provided in the goal.
+  /// and those provided in the goal.
   /// - PATH_TOLERANCE_VIOLATED and GOAL_TOLERANCE_VIOLATED: Which joint
-  ///   violated which tolerance, and by how much.
+  /// violated which tolerance, and by how much.
   rosidl_runtime_c__String error_string;
 } control_msgs__action__FollowJointTrajectory_Result;
 

libmicroros/include/control_msgs/msg/detail/joint_tolerance__struct.h

@@ -32,7 +32,7 @@ extern "C"
   * There are two special values for tolerances:
   *  * 0 - The tolerance is unspecified and will remain at whatever the default is
   * * -1 - The tolerance is "erased".  If there was a default, the joint will be
-  * allowed to move without restriction.
+  *         allowed to move without restriction.
  */
 typedef struct control_msgs__msg__JointTolerance
 {

libmicroros/include/sensor_msgs/msg/detail/camera_info__struct.h

@@ -33,8 +33,8 @@ extern "C"
   * camera namespace on topic "camera_info" and accompanied by up to five
   * image topics named:
   *
-  *   image_raw - raw data from the camera driver, possibly Bayer encoded
-  * image            - monochrome, distorted
+  * image_raw - raw data from the camera driver, possibly Bayer encoded
+  *   image            - monochrome, distorted
   * image_color      - color, distorted
   * image_rect       - monochrome, rectified
   *   image_rect_color - color, rectified
@@ -55,7 +55,7 @@ extern "C"
  */
 typedef struct sensor_msgs__msg__CameraInfo
 {
-  /// Image acquisition info                          #
+  ///                     Image acquisition info                          #
   ///
   /// Time of image acquisition, camera coordinate frame ID
   /// Header timestamp should be acquisition time of image
@@ -65,16 +65,16 @@ typedef struct sensor_msgs__msg__CameraInfo
   /// +y should point down in the image
   /// +z should point into the plane of the image
   std_msgs__msg__Header header;
-  ///                      Calibration Parameters                         #
+  /// Calibration Parameters                         #
   ///
   /// These are fixed during camera calibration. Their values will be the #
   /// same in all messages until the camera is recalibrated. Note that    #
   /// self-calibrating systems may "recalibrate" frequently.              #
-  ///                                                                     #
+  /// #
   /// The internal parameters can be used to warp a raw (distorted) image #
   /// to:                                                                 #
   ///   1. An undistorted image (requires D and K)                        #
-  ///   2. A rectified image (requires D, K, R)                           #
+  /// 2. A rectified image (requires D, K, R)                           #
   /// The projection matrix P projects 3D points into the rectified image.#
   ///
   /// The image dimensions with which the camera was calibrated.
@@ -89,7 +89,7 @@ typedef struct sensor_msgs__msg__CameraInfo
   /// For "plumb_bob", the 5 parameters are: (k1, k2, t1, t2, k3).
   rosidl_runtime_c__double__Sequence d;
   /// Intrinsic camera matrix for the raw (distorted) images.
-  ///     [fx  0 cx]
+  /// [fx  0 cx]
   /// K = [ 0 fy cy]
   ///     [ 0  0  1]
   /// Projects 3D points in the camera coordinate frame to 2D pixel
@@ -104,7 +104,7 @@ typedef struct sensor_msgs__msg__CameraInfo
   /// 3x3 row-major matrix
   double r[9];
   /// Projection/camera matrix
-  ///     [fx'  0  cx' Tx]
+  /// [fx'  0  cx' Tx]
   /// P = [ 0  fy' cy' Ty]
   /// [ 0   0   1   0]
   /// By convention, this matrix specifies the intrinsic (camera) matrix
@@ -116,39 +116,39 @@ typedef struct sensor_msgs__msg__CameraInfo
   /// For monocular cameras, Tx = Ty = 0. Normally, monocular cameras will
   ///  also have R = the identity and P[1:3,1:3] = K.
   /// For a stereo pair, the fourth column [Tx Ty 0]' is related to the
-  /// position of the optical center of the second camera in the first
-  /// camera's frame. We assume Tz = 0 so both cameras are in the same
-  ///  stereo image plane. The first camera always has Tx = Ty = 0. For
-  /// the right (second) camera of a horizontal stereo pair, Ty = 0 and
-  /// Tx = -fx' * B, where B is the baseline between the cameras.
+  ///  position of the optical center of the second camera in the first
+  ///  camera's frame. We assume Tz = 0 so both cameras are in the same
+  /// stereo image plane. The first camera always has Tx = Ty = 0. For
+  ///  the right (second) camera of a horizontal stereo pair, Ty = 0 and
+  ///  Tx = -fx' * B, where B is the baseline between the cameras.
   /// Given a 3D point [X Y Z]', the projection (x, y) of the point onto
   ///  the rectified image is given by:
-  ///  [u v w]' = P * [X Y Z 1]'
-  /// x = u / w
+  /// [u v w]' = P * [X Y Z 1]'
+  ///         x = u / w
   ///         y = v / w
-  ///  This holds for both images of a stereo pair.
+  /// This holds for both images of a stereo pair.
   /// 3x4 row-major matrix
   double p[12];
-  /// Operational Parameters                         #
+  ///                      Operational Parameters                         #
   ///
   /// These define the image region actually captured by the camera       #
   /// driver. Although they affect the geometry of the output image, they #
   /// may be changed freely without recalibrating the camera.             #
   ///
   /// Binning refers here to any camera setting which combines rectangular
   ///  neighborhoods of pixels into larger "super-pixels." It reduces the
-  ///  resolution of the output image to
-  ///  (width / binning_x) x (height / binning_y).
+  /// resolution of the output image to
+  /// (width / binning_x) x (height / binning_y).
   /// The default values binning_x = binning_y = 0 is considered the same
-  /// as binning_x = binning_y = 1 (no subsampling).
+  ///  as binning_x = binning_y = 1 (no subsampling).
   uint32_t binning_x;
   uint32_t binning_y;
   /// Region of interest (subwindow of full camera resolution), given in
-  ///  full resolution (unbinned) image coordinates. A particular ROI
+  /// full resolution (unbinned) image coordinates. A particular ROI
   /// always denotes the same window of pixels on the camera sensor,
-  ///  regardless of binning settings.
+  /// regardless of binning settings.
   /// The default setting of roi (all values 0) is considered the same as
-  /// full resolution (roi.width = width, roi.height = height).
+  ///  full resolution (roi.width = width, roi.height = height).
   sensor_msgs__msg__RegionOfInterest roi;
 } sensor_msgs__msg__CameraInfo;
 

libmicroros/include/sensor_msgs/msg/detail/channel_float32__struct.h

@@ -32,14 +32,14 @@ extern "C"
   * point.
   *
   * Channel names in existing practice include:
-  * "u", "v" - row and column (respectively) in the left stereo image.
+  *   "u", "v" - row and column (respectively) in the left stereo image.
   *              This is opposite to usual conventions but remains for
   *              historical reasons. The newer PointCloud2 message has no
   *              such problem.
   *   "rgb" - For point clouds produced by color stereo cameras. uint8
-  *           (R,G,B) values packed into the least significant 24 bits,
-  * in order.
-  * "intensity" - laser or pixel intensity.
+  * (R,G,B) values packed into the least significant 24 bits,
+  *           in order.
+  *   "intensity" - laser or pixel intensity.
   *   "distance"
  */
 typedef struct sensor_msgs__msg__ChannelFloat32

libmicroros/include/sensor_msgs/msg/detail/compressed_image__struct.h

@@ -39,7 +39,7 @@ typedef struct sensor_msgs__msg__CompressedImage
   /// +z should point into to plane of the image
   std_msgs__msg__Header header;
   /// Specifies the format of the data
-  ///   Acceptable values:
+  /// Acceptable values:
   ///     jpeg, png, tiff
   rosidl_runtime_c__String format;
   /// Compressed image buffer

libmicroros/include/sensor_msgs/msg/detail/illuminance__struct.h

@@ -34,8 +34,8 @@ extern "C"
   * All other Photometric and Radiometric measurements should not use this message.
   * This message cannot represent:
   * - Luminous intensity (candela/light source output)
-  *  - Luminance (nits/light output per area)
-  *  - Irradiance (watt/area), etc.
+  * - Luminance (nits/light output per area)
+  * - Irradiance (watt/area), etc.
  */
 typedef struct sensor_msgs__msg__Illuminance
 {

libmicroros/include/sensor_msgs/msg/detail/joint_state__struct.h

@@ -32,9 +32,9 @@ extern "C"
   * This is a message that holds data to describe the state of a set of torque controlled joints.
   *
   * The state of each joint (revolute or prismatic) is defined by:
-  * * the position of the joint (rad or m),
+  *  * the position of the joint (rad or m),
   * * the velocity of the joint (rad/s or m/s) and
-  *  * the effort that is applied in the joint (Nm or N).
+  * * the effort that is applied in the joint (Nm or N).
   *
   * Each joint is uniquely identified by its name
   * The header specifies the time at which the joint states were recorded. All the joint states

libmicroros/include/sensor_msgs/msg/detail/nav_sat_fix__struct.h

@@ -66,8 +66,8 @@ typedef struct sensor_msgs__msg__NavSatFix
   ///        sensor_msgs/TimeReference message).
   ///
   /// header.frame_id is the frame of reference reported by the satellite
-  /// receiver, usually the location of the antenna.  This is a
-  ///        Euclidean frame relative to the vehicle, not a reference
+  ///        receiver, usually the location of the antenna.  This is a
+  /// Euclidean frame relative to the vehicle, not a reference
   ///        ellipsoid.
   std_msgs__msg__Header header;
   /// Satellite fix status information.

libmicroros/include/statistics_msgs/msg/detail/metrics_message__struct.h

@@ -34,10 +34,10 @@ extern "C"
   * measure a system's CPU % for a given window yields the following data points over a window of time:
   *
   *   - average cpu %
-  * - std deviation
+  *   - std deviation
   * - min
-  * - max
-  * - sample count
+  *   - max
+  *   - sample count
   *
   * These are all represented as different 'StatisticDataPoint's.
  */

libmicroros/include/unique_identifier_msgs/msg/detail/uuid__struct.h

@@ -22,7 +22,7 @@ extern "C"
   * A universally unique identifier (UUID).
   *
   *  http://en.wikipedia.org/wiki/Universally_unique_identifier
-  *  http://tools.ietf.org/html/rfc4122.html
+  * http://tools.ietf.org/html/rfc4122.html
  */
 typedef struct unique_identifier_msgs__msg__UUID
 {

libmicroros/include/visualization_msgs/msg/detail/interactive_marker_control__struct.h

@@ -151,9 +151,9 @@ typedef struct visualization_msgs__msg__InteractiveMarkerControl
   ///
   /// Note:
   /// - The markers can be defined in an arbitrary coordinate frame,
-  /// but will be transformed into the local frame of the interactive marker.
+  ///   but will be transformed into the local frame of the interactive marker.
   /// - If the header of a marker is empty, its pose will be interpreted as
-  /// relative to the pose of the parent interactive marker.
+  ///   relative to the pose of the parent interactive marker.
   visualization_msgs__msg__Marker__Sequence markers;
   /// In VIEW_FACING mode, set this to true if you don't want the markers
   /// to be aligned with the camera view point. The markers will show up

libmicroros/include/visualization_msgs/msg/detail/interactive_marker_update__struct.h

@@ -21,8 +21,8 @@ extern "C"
 /**
   * Type holds the purpose of this message.  It must be one of UPDATE or KEEP_ALIVE.
   * UPDATE: Incremental update to previous state.
-  *         The sequence number must be 1 higher than for
-  *         the previous update.
+  * The sequence number must be 1 higher than for
+  * the previous update.
   * KEEP_ALIVE: Indicates the that the server is still living.
   *             The sequence number does not increase.
   *             No payload data should be filled out (markers, poses, or erases).
@@ -58,7 +58,7 @@ typedef struct visualization_msgs__msg__InteractiveMarkerUpdate
   uint64_t seq_num;
   uint8_t type;
   /// Note: No guarantees on the order of processing.
-  /// Contents must be kept consistent by sender.
+  ///       Contents must be kept consistent by sender.
   /// Markers to be added or updated
   visualization_msgs__msg__InteractiveMarker__Sequence markers;
   /// Poses of markers that should be moved

libmicroros/include/visualization_msgs/msg/detail/marker__struct.h

@@ -143,7 +143,7 @@ enum
 /**
   * See:
   * - http://www.ros.org/wiki/rviz/DisplayTypes/Marker
-  * - http://www.ros.org/wiki/rviz/Tutorials/Markers%3A%20Basic%20Shapes
+  *  - http://www.ros.org/wiki/rviz/Tutorials/Markers%3A%20Basic%20Shapes
   *
   * for more information on using this message with rviz.
  */
@@ -159,10 +159,10 @@ typedef struct visualization_msgs__msg__Marker
   /// Type of object.
   int32_t type;
   /// Action to take; one of:
-  ///  - 0 add/modify an object
-  /// - 1 (deprecated)
-  /// - 2 deletes an object (with the given ns and id)
-  /// - 3 deletes all objects (or those with the given ns if any)
+  /// - 0 add/modify an object
+  ///  - 1 (deprecated)
+  ///  - 2 deletes an object (with the given ns and id)
+  ///  - 3 deletes all objects (or those with the given ns if any)
   int32_t action;
   /// Pose of the object with respect the frame_id specified in the header.
   geometry_msgs__msg__Pose pose;
@@ -197,7 +197,7 @@ typedef struct visualization_msgs__msg__Marker
   /// Similar to texture_resource, mesh_resource uses resource retriever to load a mesh.
   /// Optionally, a mesh file can be sent in-message via the mesh_file field. If doing so,
   /// use the following format for mesh_resource:
-  ///   "embedded://mesh_name"
+  /// "embedded://mesh_name"
   rosidl_runtime_c__String mesh_resource;
   visualization_msgs__msg__MeshFile mesh_file;
   bool mesh_use_embedded_materials;

libmicroros/include/visualization_msgs/msg/detail/menu_entry__struct.h

@@ -65,20 +65,20 @@ enum
   *   parent_id = 0
   *   title = "fun"
   * - id = 2
-  * parent_id = 0
-  * title = "robot"
+  *   parent_id = 0
+  *   title = "robot"
   * - id = 4
   * parent_id = 2
-  * title = "pr2"
+  *   title = "pr2"
   * - id = 5
   * parent_id = 2
   *   title = "turtle"
   *
   * Gives a menu tree like this:
-  *  - fun
-  *  - robot
-  * - pr2
-  *    - turtle
+  * - fun
+  * - robot
+  *    - pr2
+  * - turtle
  */
 typedef struct visualization_msgs__msg__MenuEntry
 {