-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ODCL node on vehicle #54
Comments
To be clear, the node that does this will still be in 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. |
Going to change how data is returned from |
Does 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 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. |
@rland93 There are no signs that VideoCapture performs lossy compression when we poll images from camera. cv2.VideoCapture(0) reads from the linux file /dev/video0 which is location of camera sensor if it has been identified on computer. It might be confusing because there's a lot of terms like "video" thrown around, but I think opencv just means capturing image sequences whether live or from a file that contains image sequences. We are not reading from any files, so we should be good. |
Once an ODCL is found by the pipeline, it needs to be published. We need a node that runs on the vehicle, which:
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.
The text was updated successfully, but these errors were encountered: