-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Computer vision framework #1328
Conversation
…thods can be added to the computer vision thread
*/ | ||
|
||
/** | ||
* @file modules/computer_vision/cv.h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plz fix file path
also please make use two spaces indent
I guess the viewvideo_nps.c could be removed (it doesn't do anything anyway) and the modules disabled for the nps target... |
I would like to implement viewvideo_nps instead of removing it. |
even better, although I wonder a bit what the random image will be good for ;-) |
Maybe you can somehow link it with flight gear and get some kind of video from the "cabin"? |
Looks good to me, without having had the chance to actually test it.... |
@flixr obviously the test image is not very useful indeed, but allows checking of the computer vision routines in simulation. Note that the video_thread code from AP can also run in linux, showing your webcam image while simulating. Not sure how this should be done when you have 3 options for the simulation code: 1) (no vision in nps) 2) video_thread_nps (test image or flightgear/ROS/smartuav coupling), 3) webcam. |
Conflicts: conf/airframes/BR/bebop_indi.xml sw/airborne/modules/computer_vision/viewvideo.c
instead of having many new copies of the same, a computer vision framework is initiated:
video_thread
which can run one or more computer vision modules (e.g. rtp_stream or qrcode or opticflow)