CreOS SDK
The CreOS SDK allows you to interact with Avular robots
 
Loading...
Searching...
No Matches
channel_float32.hpp
Go to the documentation of this file.
1
8namespace sensor_msgs::msg {
31public:
32 // This message is used by the PointCloud message to hold optional data
33 // associated with each point in the cloud. The length of the values
34 // array should be the same as the length of the points array in the
35 // PointCloud, and each value should be associated with the corresponding
36 // point.
37 //
38 // Channel names in existing practice include:
39 // "u", "v" - row and column (respectively) in the left stereo image.
40 // This is opposite to usual conventions but remains for
41 // historical reasons. The newer PointCloud2 message has no
42 // such problem.
43 // "rgb" - For point clouds produced by color stereo cameras. uint8
44 // (R,G,B) values packed into the least significant 24 bits,
45 // in order.
46 // "intensity" - laser or pixel intensity.
47 // "distance"
48
49 // The channel name should give semantics of the channel (e.g.
50 // "intensity" instead of "value").
51 std::string name;
52
53 // The values array should be 1-1 with the elements of the associated
54 // PointCloud.
55 std::vector<float> values;
56};
57} // namespace sensor_msgs::msg
ROS message class definition for ChannelFloat32.
Definition channel_float32.hpp:30
message definitions of the sensor_msgs package
Definition battery_state.hpp:8