View Single Post
  #5   Spotlight this post!  
Unread 09-04-2009, 21:54
RyanCahoon's Avatar
RyanCahoon RyanCahoon is offline
Disassembling my prior presumptions
FRC #0766 (M-A Bears)
Team Role: Engineer
 
Join Date: Dec 2007
Rookie Year: 2007
Location: Mountain View
Posts: 689
RyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond reputeRyanCahoon has a reputation beyond repute
Re: Bug Algorithms for Autonomous

My thoughts on bug algorithms in FIRST:
They perhaps are not so well suited for our environment:
--Most of the big obstacles on the field (robots, field elements) are moving (fast!)
--Except for the fast moving obstacles, we already know a map of the environment, which makes dead reckoning a better approach

However, I think they could be a fun way to teach beginning programmers, as they can be fairly simple algorithms to write - i.e. if antennae sensor is bumped, reverse direction. Thus, you can get some really interesting behaviors given very little coding, which is the key for getting kids interested in something challenging like programming. Could be especially effective given some of the concepts they could introduce.

Thoughts on implementation:
Sounds like a really good usage for state machines to me, at least based on the examples given in the presentation that [Ken Streeter] linked to.

I might have to try these with my own teams.
--Ryan
__________________
FRC 2046, 2007-2008, Student member
FRC 1708, 2009-2012, College mentor; 2013-2014, Mentor
FRC 766, 2015-, Mentor