ODCL node on vehicle

[rland93]

Once an ODCL is found by the pipeline, it needs to be published. We need a node that runs on the vehicle, which:

• Takes a picture with the camera
• Runs the pipeline on the picture
• Gets the ODCLs from the pipeline and parses them into a ROS message
• Publishes the ROS message to a topic**

It will do all of this in a loop as quickly as possible while the node is running.

** They do need to be also serialized with MAVROS. Not sure how that works yet.

[rland93]

To be clear, the node that does this will still be in ROS (or, ROS-dev), not in a separate branch or repo.

We will git clone ROS-dev onto both the ground and the vehicle, and we can just run the ground-based nodes on one and the vehicle nodes on the other.

[rland93]

Going to change how data is returned from pipeline.run list -> dict

[rland93]

@dangthanhan507

Does cv.VideoCapture() capture a video stream or still images? I notice that the resolution is being set manually.

Video streams are almost always lossy compressed by the on-board video coprocessor -- there's usually no way to get the "raw" video stream, only the downscaled and lossy h264, which is a very poor substitute (ie 1080/720p instead of 4000x3000 or whatever)

Since we are using the tiler, we will want to be working with images -- NOT the lossy video.

If it's a video stream, that will need to be changed to captureImage(), if openCV has such a functionality. Or else, we will need to figure out how to capture image directly to file and then read the image file statefully from inside of our script.

Cameras usually limit the number of pictures that can be taken per second so that the on-camera image chips don't heat up too much. For us, that's not likely to be an issue, since the inference rate for a tiled image is somewhere around 1hz.