Quote:
Originally Posted by AlexanderTheOK
While I don't gamble out of principle, I would wager a rather large sum of money that the 2016 FRC game will, in fact, happen indoors, although I have to agree that polycarbonate is a nuisance.
If this years game happens outdoors I'll eat my hat and post progress pics.
|
Haha. True I doubt the game will be outdoors, but from personal experience there are fields hosted at places with large windows that throughout the day the sun will illuminate and cast shadows on the field or blind the robot. And yes, this would effect most any camera system, but I believe an IR camera looking for a pattern would be affected the most vs a normal RGB camera.
Water game confirmed? Am I doing this right?
Quote:
Originally Posted by AlexanderTheOK
Running rather well optimized SLAM code with the Kinect (and an Xtion Pro) on the ODROID U3 nets between 5 and 15 FPS. I imagine I could get it higher but I have other projects I need to work on. I think you are either severely overestimating the capabilities of modern single board computers, or severely underestimating the amount of work a computer has to do to do anything meaningful with a pointcloud.
|
As this is the FIRST community I bet everyone here would love to see you share your code rather then just talk about it. I understand that to work with the pointcloud does take processing power, but you too might be underestimating how far SoC boards have come since the ODROID U3. The thing about the ZED is that it requires a NVIDIA GPU to function meaning to use it on a robot a team will need a NVIDIA Jetson TK1 or even better the new Jetson TX1. So no, a team will not get 120 FPS on the robot, but the fact that the camera would be able to capture at that speed would reduce motion blur. Last year with our horribly optimized cascade classifying code we were getting ~15-25 FPS for green bin detection on a Jetson TK1 and a USB camera.