jsbruglie / gap Goto Github PK

For total compatibility with Gazebo, we should use the same license.
I plan on doing this very soon.
It involves changing the header of each source file, so keep that in mind if altering the code in a separate branch.

Hi there,

I am just writing this issue to tell you to follow the steps you described in the documentation of this project and also of the tf-shape-detection project. Please try to follow them exactly as you described. I am pretty sure you won't achieve anything.

I am glad that you worked on these awesome projects, but it's so sad that you can't write a proper documentation or atleast some clear usage steps.

Have an awesome day!

Your code is awesome but I wonder where did you find the API about "gazebo::msgs::Visual"?

At the moment, storing captured camera frames on the disk seems to be the bottleneck of the pipeline. One possible solution: the camera plugin could rely on a buffer (e.g. FIFO queue) that keeps captured images in memory and a dedicated worker thread for saving those images to disk. @jsbruglie what do you think?

Installing the plugin was an extremely thorny experience because of OpenCV. I used (2.4.9.1) and I had to modify many things. Maybe just specify exactly which version of OpenCV you used, or even better, migrate to OpenCV 3.3.0 😉

Attempting to run scene_example, ubuntu 18.04, gazebo 9.0.0, running spawner.world in gzserver.
Code stalls at line 143 of scene_example.cc pub_camera->WaitForConnection();

This is needed for proper dependency check and to import our tools as an external library for 3rd party projects.
Catkinizing the package may also be useful, so it can be easily integrated into the ROS work flow and compiled from a catkin workspace.
Current temporary solution in 1a104cd.

In the capture example client I randomly get the terminal output:

Master Unknown message type[] From[60586]
[libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp, type, serialized_data

However everything seems to work.
Gazebo's own issue 821 seems to address this and suggests it is a race condition.