Chief Delphi - Finding where you are in the field

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- Technical Discussion (http://www.chiefdelphi.com/forums/forumdisplay.php?f=22)

- - Finding where you are in the field (http://www.chiefdelphi.com/forums/showthread.php?t=99547)

Re: Finding where you are in the field

Quote:

Originally Posted by Ross3098 (Post 1104306)

Ive been thinking about setting up localization/field coordinate system for this game. The only problem I can see is the bump causing some of the wheels to be off the ground and the encoders giving inaccurate measurements.

I'm trying very hard to figure a way around this issue because I have absolutely no idea how to do vision tracking in C++ this year.

In the "real world" of mobile robotics, typically you would deal with this problem doing some sort of sensor fusion.

Basically, if you look at each of the sensors available to us, they are all useful for localization but none of them is perfect:

* Gyros/Accelerometers: Very fast response and good accuracy initially, but by integrating accelerations and velocities over time, they drift.

* Encoders: Very precise distance/speed measurements...as long as your wheels don't slip and you know the precise diameter of your wheels.

* Vision system: Seeing a known "landmark" like the goal tells you a great deal about your absolute position on the field, but you can't always see the goal, and you will sometimes get false alarms depending on the environment.

In robotics, we often find robots with this arrangement of sensors. By fusing their outputs together, you can get a system that compensates for the individual failings of each sensor. For example, you might use your gyro for most of your heading measurements, but if you get a good shot of the goal, you "reset" your gyro to reduce/eliminate drift. Common fusion techniques include Extended and Unscented Kalman Filters. Unfortunately, getting these systems working is a Masters/PhD level challenge, and would be difficult to get working well in 6 weeks for anyone (especially since you won't have a testable robot for much of that time).

That said, I am hoping that at least a few ultra high end teams take on this challenge (I'm looking at you, 254).

Jared

Re: Finding where you are in the field

Quote:

Originally Posted by Jared341 (Post 1104313)

* Vision system: Seeing a known "landmark" like the goal tells you a great deal about your absolute position on the field, but you can't always see the goal, and you will sometimes get false alarms depending on the environment.

Stereo vision? Distortions? This one seem somewhat difficult to integrate.

Quote:

I've been pondering, why would stereo vision be difficult? Is it due to the improbability of connecting two cameras to the D-Link or is it due to the difficulty in simply using the two cameras?

Stereo vision has a couple of steps. First is positioning the 2 cameras just right and get a very accurate measurement of the distance between the 2. Secondly, numerous algorithms that's entirely non-trivial will be needed to locate "things" in the 2 images and compare their location in the 2 images to get the distance of those objects

Even though it doesn't sound difficult, it is very tough to do in practise.

Re: Finding where you are in the field

I think the group of people here who believe that they can rely soly on the vision target that is significantly behind the basket do not understand what happens when you move to either side rather than shooting straight on. THAT is why field awareness will be usefull, unless you plan on shooting only from the key.