You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Followup to #62 and #92 . Now that we have revamped the Executors and CallbackGroups, the other part of ROS2's architecture that may be causing issues is our QualityOfService settings. In many cases, we just stick to a pre-implemented QoS, or we just pass in a queue length like 1, without thinking intentionally about what guarentees we want in each dimension of the QoS policy. This Issue is to address that.
The text was updated successfully, but these errors were encountered:
Followup to #62 and #92 . Now that we have revamped the Executors and CallbackGroups, the other part of ROS2's architecture that may be causing issues is our QualityOfService settings. In many cases, we just stick to a pre-implemented QoS, or we just pass in a queue length like 1, without thinking intentionally about what guarentees we want in each dimension of the QoS policy. This Issue is to address that.
The text was updated successfully, but these errors were encountered: