|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Why even Go with the kinect?
Instead of viewing it as a control method, we view it as a start/stop mechanism. Last year in autonomous, we had many problems with field calibration that lead to a couple big penalties from putting an ubertube in an opposing feeding lane. The way I look at it, the Kinect is a way to avoid that. You can program a simple command to realign the robot a tad to save the hybrid mode
|
|
#2
|
|||
|
|||
|
Re: Why even Go with the kinect?
To be honest, incorporating the kinect into our program will probably only happen in two ways:
1. Attach it to the robot to do some kind of vision tracking. 2. Use it to see an epic pose made by our human player so it starts the program. I don't think we're going to bank on using the kinect and i really don't tink we're going to be using more than one motion if we go with the kinect. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|