1 22 14 Notes

rule loophole, robot pushes other robots with ball, counts as possession
for autoaim, we need to know what others use to catch the ball
project images of boxes for robots using relative positions and field, in order to draw arcs and trajectories for shooting
piston and springs is current shooter
make bubble of counter magnetic field to make sure compass works
use kinect tracking from driver's station, use blinking light on robot to track position
someone has to look up driver's station no computing?
how to pass?
use pictures of alliance robots to overlay known positions of allied robots
real-time predict other robots' trajectories
use stylus to plan path
calculate other robots' kinetic energy, predict where it can go
greatest difficulty is predicting what others are doing, control other robots?
give alliance members our code, easier for predicting movement, check if allowed?, our code can be used against us
what about path planning and absolute control (independent of robot direction, only based on driver direction)
put camera outside of stage allowed?
persistent storage on robot to load data, web interface
driver options, future view on/off, control scheme
robot profiler
not sure how to tell which robot is which on same alliance
look for distinguishing features (e.g. forklift), takes too much code and processing power
analyze other robots during 10 second autonomous
look up possible positions for mounting camera on drive station ?
check if you can have camera with driver ?
broadcasting devices must be specifically cleared by FIRST beforehand via email (sent)
set up LAN router
must stop skidding, must know acceleration
must have control over robot to do gui thing
create warning system to prevent skidding, make automatic instead
brake for mecanum wheel or grippy thing, must still prevent skid

features:
future view
autonomous
auto aim
anti skid
robot tracking