20182

What is something that you think is unique about your robot this season? What about your robot do you think would make it stand out at competition?

Two claw system with custom rack and pinion claws. OTOS odometry

What types of Outreach do you plan to do for this season? Which of those Outreach initiatives are you most proud of?

We did a community outreach with a local organization that specializes in enriching the lives of children with Autism Spectrum Disorder. We also are connected with University of Missouri Science and Technology Kummer Institute for k-12 STEM outreach

Describe an element of your code which you think will be most advantageous to your performance over the season.

Single button activation for multiple actions. Exmaple we can switch our chamber hanging routine to our high basket routine with a push of a button. All of those actions are encoder controlled or the servo limits are set. We do not manually control our actuators.

What competitions will you be attending? Which of the ones that you listed are you looking forward to the most?

3 league meets, STL South League Tournament, STL super Qualifier, MO/KS state meet. We also will re-apply for the Robot Rumble at Gateway International Speedway. We look forward to our local STL South League Tournament because we are the host.

How will you be organizing your team at competitions?

Pit, Drive, Scout, Media,

Describe a unique or noteworthy strategic device or element that you think would be useful for this game.

We believe that having two sperate systems doing two different operations was a good choice. In case of failure with one system the other system can operate indipendently and allow to continue to score points.

How would you describe your design process? How many options/strategies do you compare? How do you visualize your designs before building?

We approach the game as a true engineering challenge, where every opinion is supported by analysis and data. If someone questions an idea, they are expected to propose a viable solution in return. Our concepts are grounded in physics, mathematics, and practical experience. Through research and development, we evaluate whether a concept is worth further refinement or if we should pivot to explore new ideas. We don’t get attached to initial ideas, recognizing that the best solutions often emerge through iteration. While some concepts may be exciting, we prioritize designs that are not only creative but also practical, reliable, and achievable in the real world.

How do you divide your team's time between things like design, building, programming etc. Do you enforce this timing? If so, why?

Design=25% Build = 25% Programing=30% drive practice= 20%