Team Nine/Final Paper

From Maslab 2015
(Difference between revisions)
Jump to: navigation, search
(Paper)
(Paper)
Line 1: Line 1:
 
== Paper ==
 
== Paper ==
blah blah
 
  
 
===== Introduction =====
 
===== Introduction =====
blah blah
+
Team 9 (i.e. Team Underpowered -- U.P.) consists of three practical and mechanically-savvy AeroAstro students and two C.S. rockstars. We formed because of strong UROP, fraternity, and course major ties, but we stayed together and finished strong because of our mutual respect and dedication to our beloved robot. With Kurtzy, Tratt, and E.Jordan spearheading the design of the mechanical monster and Sandy + Lerner = let there be code, our team subdivides based on expertise to great effect. 3D printing blackbelt Kurtzy, also the woodshop master at Simmons, has the most experience with fabrication and assembly of badass projects. Resident chess expert Tratt helps with the strategic sacrifices. E.Jordan definitely carries the team when it comes to being lolzy. Sandy Cheeks cannot be bothered to debug since his code is so darn fly. Why is he called Lerner? Since he already learned everything he needs to know. In kindergarten.
  
 
===== Strategy Rationale =====
 
===== Strategy Rationale =====
 +
Imagine you have two stacks, one red and one green, with n blocks each. If you pick up a stack of 3 blocks, 2 red and 1 green, is it more beneficial to sort them and increased n^2 or to place them on the central table as a stack of 3? Given that the table option increased the score multiplier, unless n is less than or equal to 3, then it is beneficial to place the stack on the table. Our initial thoughts centered on maximizing points, but our final strategy is to score in all possible ways, using two tall canisters to sort and stack the blocks while placing a stack on the center table to obtain the 3x multiplier if possible. Stacking the blocks flush with the ground at all times ensures point scoring even in the event of catastrophic robot failure. Tolerances on key hardware such as stack canisters, claw, and dispenser mechanism are engineered such that passive geometries will enable 100% success rates in block flow without jamming. Software is created as simply as possible to increase robustness; simple wall following and Boolean block finding methods enable easy block collection with minimal efficiency sacrifices. Our goal is to collect all block stacks, place one with our color at the top on a middle table, and deposit one large stack in the purple area to score with the opponent's color while scoring with our color at our end position on the field.
  
 
===== Key Hardware =====
 
===== Key Hardware =====
 +
  
 
===== Software Development =====
 
===== Software Development =====

Revision as of 23:11, 26 January 2015

Contents

Paper

Introduction

Team 9 (i.e. Team Underpowered -- U.P.) consists of three practical and mechanically-savvy AeroAstro students and two C.S. rockstars. We formed because of strong UROP, fraternity, and course major ties, but we stayed together and finished strong because of our mutual respect and dedication to our beloved robot. With Kurtzy, Tratt, and E.Jordan spearheading the design of the mechanical monster and Sandy + Lerner = let there be code, our team subdivides based on expertise to great effect. 3D printing blackbelt Kurtzy, also the woodshop master at Simmons, has the most experience with fabrication and assembly of badass projects. Resident chess expert Tratt helps with the strategic sacrifices. E.Jordan definitely carries the team when it comes to being lolzy. Sandy Cheeks cannot be bothered to debug since his code is so darn fly. Why is he called Lerner? Since he already learned everything he needs to know. In kindergarten.

Strategy Rationale

Imagine you have two stacks, one red and one green, with n blocks each. If you pick up a stack of 3 blocks, 2 red and 1 green, is it more beneficial to sort them and increased n^2 or to place them on the central table as a stack of 3? Given that the table option increased the score multiplier, unless n is less than or equal to 3, then it is beneficial to place the stack on the table. Our initial thoughts centered on maximizing points, but our final strategy is to score in all possible ways, using two tall canisters to sort and stack the blocks while placing a stack on the center table to obtain the 3x multiplier if possible. Stacking the blocks flush with the ground at all times ensures point scoring even in the event of catastrophic robot failure. Tolerances on key hardware such as stack canisters, claw, and dispenser mechanism are engineered such that passive geometries will enable 100% success rates in block flow without jamming. Software is created as simply as possible to increase robustness; simple wall following and Boolean block finding methods enable easy block collection with minimal efficiency sacrifices. Our goal is to collect all block stacks, place one with our color at the top on a middle table, and deposit one large stack in the purple area to score with the opponent's color while scoring with our color at our end position on the field.

Key Hardware
Software Development
Competition Performance
Reflections and Tips
Conclusion