Skip to content
#

ros2

Here are 843 public repositories matching this topic...

SteveMacenski
SteveMacenski commented Nov 10, 2020

Hi,

I figured I'd ask and see if there was interest in something like this. In order to help remove salt and pepper noise from images, typically you might use dilation and erosion. The same concept could apply to navigation2 costmap layers, where an erroneous voxel layer or obstacle layer measurement (or static layer with SLAM session and things moving around) would make in the middle of free s

help wanted good first issue in progress
iceoryx
dkroenke
dkroenke commented May 20, 2022

Brief feature description

Since we have some CMake code to maintain, it make sense to enforce on this code also code quality rules like we do with the C++ code.

A possible tool-framework could be cmakelang which offers tooling for formatting and linting CMake Code properly.
Other suggestions are always welcome.

Detailed i

good first issue tooling
IsaacBlankenau
IsaacBlankenau commented Jun 29, 2022

We find the Map panel very useful for displaying multiple robots. The change to show different topics in different colors was a big improvement, but having more control over the color would be very helpful in our case. Currently, the color seems to be chosen based on the order the topic appears, which can vary and takes some additional time each run to figure out which point corresponds with which

feature panel: map good first issue
JEnoch
JEnoch commented May 16, 2022

Describe the feature

In current implementation, when issuing a query, the QueryingSubscriber pushes in a merge_queue the samples resulting of this query and the samples coming directly from the publishers. Then, at query end, the merge_queue is sorted and dedup-ed.

I would be more efficient to use an enhanced merge_queue that sort+dedup on the fly, for each pushed sample.

enhancement good first issue
gz-sim
mjcarroll
mjcarroll commented Jun 16, 2022

I noticed a bit of an inconsistency when implementing some MBZIRC functionality.

Description

  • Expected behavior: Other sensors such as the magnetometer and air pressure sensor set gazebo::components::SensorTopic component. This allows the sensor topic to be retrieved by other consumers of the ECM. Rendering sensors should be the same and set their respective topic component (or namesp
bug good first issue help wanted rendering
KeisukeShima
KeisukeShima commented Feb 16, 2022

Motivation

autoware_testing provides basic tests that can be used in common for all packages.
However, the current implementation is only a smoke_test, and what can be checked with this test is limited.
I read an issue on Autoware.Auto about the design of autoware_testing (link) and thought it could be

enhancement good first issue

Improve this page

Add a description, image, and links to the ros2 topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the ros2 topic, visit your repo's landing page and select "manage topics."

Learn more