I want to ask if it would be better if a non-default QoS profile would be better for Image publishers. Current publishers in the master branch have the Default Qos Profile with a depth of 100.
|
rclcpp::QoS {100}.get_rmw_qos_profile()))), |
|
std::string(BASE_TOPIC_NAME) + "/compressed", rclcpp::QoS(100)); |
|
m_compressed_cam_info_publisher = |
|
this->create_publisher<sensor_msgs::msg::CameraInfo>( |
|
"camera_info", rclcpp::QoS(100)); |
Ideas:
- I think a lower depth would be better in some cases.
- For the same reason, I would like to make the QoS profile configurable.
- Or enable qos_override in the rlcpp node.
If reasonable, I can make a PR.
I want to ask if it would be better if a non-default QoS profile would be better for Image publishers. Current publishers in the master branch have the Default Qos Profile with a depth of 100.
usb_cam/src/usb_cam_node.cpp
Line 49 in 1091c5b
usb_cam/src/usb_cam_node.cpp
Lines 186 to 189 in 1091c5b
Ideas:
If reasonable, I can make a PR.