OUR SEASON 

____________________________________________________________________________________________________________________________________________________________________________________________________

Our Robot

Overview

Prometheus


____________________________________________________________________________________________________________________________________________________________________________________________________

Events

Competitions

11/11/23 - League Event 1

12/9/23 -  League Event 2 

1/13/24 -  League Event 3

1/27/24 -  League Tournament

2/3/24 -   Semi Area Qualifiers 


Click on the image above to learn more about FTC Competition types

2/10/24 - Semi Area Qualifiers (Austin)

2/24/24 - Area Championships 

3/22/24 - UIL State Championships

3/23 - 3/24 - FIRST State Championships

4/16 - 4/20 - World Championships


____________________________________________________________________________________________________________________________________________________________________________________________________







Outreach




3M

Date/Time: Wednesday, August 30, 2023 | 4:30pm - 5:30pm

Overview: Today, we toured a 3M facility near us. We were able to not only learn about the various products that 3M creates, but also how they made them. We were able to learn about the design process and how 3M uses that to not only improve their products, but also design new products. 

We can apply this to this season as we are creating a new robot completely from scratch, so it’s important to utilize the design process to make sure our brainstorming process is as organized as possible, everybody gets to share their ideas, and we can come up with a unique and robust design. 

Dell Rugged Labs

Date/Time: Monday, November 6, 2023 

 10:00 pm - 11:30 pm 

Overview: Today, the team had the opportunity to talk to Dell about their Rugged Lab, which is where they test their Rugged products such as the Rugged computer, which is made to withstand various harsh conditions. Not only did we learn about the machinery they use such as the extreme temperature chamber and the micro dropper, but we also learned about the “use case.” Dell described a use case as identifying scenarios in which your technology would be used. While their Rugged computers might be used by marine biologists and would therefore need to be relatively water resistant, our robot would be used to, primarily, place pixels on the backboard, meaning it would need to have a strong and stable intake and lift system. We also learned that in order to do testing effectively, you need to test for failure rather than for success. 



Microsoft

Date/Time: Thursday, September 14, 2023 | 4:30pm-5:30pm

Overview: Today our team went to the Microsoft Corporation compound at Quarry Oaks ||. There, we met the Engineering Site Lead and Database Software Designer, Connor Cunningham, who Happily showed us the Ins and outs of not only Microsoft, but the database centers that power our banks, businesses, websites, and statistics. 

Management: When even a slight mix up in the efficient and speedy SQL code can cause a nationwide bank rush or stock market crash, it’s important that the teams working there have incredible communication with each other and other teams across the world to keep things up and running. Deadlines must not be crossed empty handed, and nothing can get changed without a lot of testing and double-checking. We learned that in order to meet deadlines, you may have to shrink the scope or results of your work, or increase the time given to work on it, in order to keep your team complaint-free!

Software: although the SQL coding language is more advanced and mainly used for blockchain-like programs over sensors and moving parts, we were able to learn plenty about problem solving related to software. First off, each software member must focus on the problems your good at, while having all the background knowledge to be able to solve others. Secondly, research and a quick history lesson may be necessary to find that the way you’ve talking a goal has been all wrong, and make your code much more manageable and convenient. Always be ready to backtrack and check your work! 

____________________________________________________________________________________________________________________________________________________________________________________________________