View Single Post
  #25   Spotlight this post!  
Unread 03-17-2016, 01:23 PM
engunneer's Avatar
engunneer engunneer is offline
Alumni turned Mentor
AKA: Branden Gunn
FRC #4761
Team Role: Mentor
 
Join Date: Jan 2007
Rookie Year: 1996
Location: Reading, MA
Posts: 729
engunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond reputeengunneer has a reputation beyond repute
Re: Rethinking the Low bar

Quote:
Originally Posted by Trevor1523 View Post
Right after we watched the reveal video on the 9th we went to 179's field to see what it looked like. When I saw the height of the low bar I looked at one of my team mates and said "There's no way we're fitting under that". I would probably still have the same reaction.

For me, the low bar is an obstacle that I personally knew most teams would design their robot for because "OOOOHHH WE GOTTA DO EVERTHIN'". So we decided not to. I think we would make that decision again. Even with our #tallbot we still had trouble packaging everything into what we built so kudos to all those low bar robots.

EDIT: I've been wanting to say this for a while and I feel like this is an appropriate place to say it:
The low bar is a defence, yes? Yes. So I looked at the problem as would we design our robot to just be able to damage one defence, say the Portcullis. That Portcullis design is essentially your constraint and you can't remove it, you can't work around it. It has to stay there. So we decided to not let 1 defence constrain us when there are 8 other ones that are available to take down. (I think that makes sense)
Counter argument: our design goal was to be able to breach alone, and we picked low bar instead of c class defenses. It means we I ly have to be capable of 7/9 of the defenses instead of 8/9 which would be needed for a solo breaching #tallbot.

I told my students on day two that the game isn't hard per se, but it is a difficult packaging problem, which is very common in engineering.
__________________
Student FRC23 (1996-1999), Mentor FRC246 (2000), Mentor FRC1318 (2007-2009), Mentor FRC93 (2011), Mentor FRC2151 (2012), Mentor FRC23 (2013), Mentor FRC4761 (2014-2017)
1998 - National Chairman's Award and Woodie Flowers Award (FRC23, Mike Bastoni ) | 2007 - PNW SF (488, 1595) | 2008 - Oregon RCA - Seattle #2 Seed, SF (488, 1696) | 2009 - Oregon #1 Seed, Winners (1983, 2635) - Seattle SF (945, 2865) - Galileo #2 Seed, SF (973, 25) | 2012 Midwest F (111, 71) | 2014 RIDE Winners (78, 125), Inspector - NEU #24, QF (3479, 3958) - NECMP #35 | 2015 Reading #11, SF (1058, 190), Inspector - RIDE #17, QF(4055, 5494), Inspector - NECMP #57 | 2016 Reading #4, SF (133, 4474), DCA, Inspector - Ride #22, SF (1735, 2067), Creativity, Inspector - NECMP #48, RCA - Archimedes
Reply With Quote