Y’all have your CAD anywhere?
You guys are great we competed aginst you are beat our butts. Keep up the great work
CHS District Blacksburg VA Event 2024
Beginning our recap from Friday afternoon, the team embarked on a journey to Blacksburg, Virginia, with approximately a three and a half hour drive. This marked a significant milestone as it was the team’s inaugural event. Remarkably, we arranged lodging at an entire villa located just 15 minutes away from the venue. The villa had a full commercial kitchen along with a smaller one, which proved instrumental as our parents took charge of meal prep for the entire weekend! This setup facilitated strategy sessions and provided valuable downtime for the team at the close of each day.
Load-In:
Upon arrival at 5:30 PM with our trailer, the volunteers warmly greeted us, streamlining the process of unloading and setting up our pit. Within less than 20 minutes, our equipment was smoothly rolled out of the trailer and into our designated area, setting the tone for a stress-free load-in experience!
Robot Inspection:
Following the setup of our pit, we promptly engaged with the robot inspectors to initiate the inspection process. Our robot weighed in at 93.8 pounds, and due to its streamlined design this year, inspection took a mere seven minutes. With no pneumatics, extending arms beyond the chassis, or sharp edges, our robot easily cleared the inspection hurdles. Subsequently, we familiarized ourselves with the venue layout, got to be on the field on-person to understand its nuances, and located the practice field for Saturday’s sessions. Engaging with other teams allowed us to forge new relationships and cultivate friendships early on, laying a solid foundation for collaborative endeavors ahead.
Saturday morning kicked off with two guaranteed practice matches, but our team seized the opportunity to secure an additional practice round, totaling three matches. This allowed us to test out different autonomous modes, including our four-piece and one-piece sneak autos. Following these trials, we participated in the Opening Ceremonies, where our very own Addison and Michaela, alongside fellow students from other teams, delivered a stirring rendition of the national anthem.
Qualification Matches Commence:
Our journey through the qualification matches began with a triumphant victory in match 3, securing a score of 45 to 38. In match 9, we continued our winning streak with a score of 32 to 57. However, the real challenge awaited us in match 11, pitting us against formidable opponents: rank 5 at the event, 1086 Blue Cheese, rank 2, 1629 GACO Robotics, and rank 3, 5804 Torch. Despite our valiant efforts, we fell short in this match, earning 56 points to our opponents’ 63.
Smooth sailing characterized most of our qualification matches until match 31, where we suffered severe damage to our intake due to a collision with 5804.
We regrouped, sought assistance from fellow teams for spare parts, and managed to repair our intake in time for match 42, where we staged a remarkable comeback, securing victories in our remaining three matches of the day.
End of day 1 after having lost our intake in match 31 we wanted to have an emergency plan for if this ever happened again in a match. And we know that our geometry could theoretically allow us to have a source intake but we had not programmed this function. So that evening we spent some time at the practice field getting this function running and validated so we would be prepared for anything that tomorrow could bring.
As evening descended, we reconvened at the villa for brainstorming sessions, delving into alliance selection strategies and identifying compatible teams. Despite holding the top rank at the event, we remained vigilant, recognizing the fluidity of rankings and the importance of consistency. With five more qualification matches slated for Sunday, our focus remained unwavering as we aimed to maintain our momentum and secure our position in the competition.
Sunday Qualifications and Playoffs:
Kicking off the morning, we engaged in crucial discussions with various teams, gathering insights on their autonomous capabilities, spare parts availability, and overall readiness for potential alliance selections. After consulting with five different teams and analyzing the collected data, the strategy team convened to deliberate on the findings. While there were numerous impressive teams with high-scoring robots, our focus zeroed in on Team 449 due to the promising compatibility of their two-piece Centerline Auto, which perfectly complemented our four-piece close Auto, potentially yielding a substantial 39 points in autonomous.
Following the conclusion of the final qualification matches, we successfully maintained our position at the top spot, with a remarkable Effective Power Average (EPA) of 2.44 and an average match score of 54 points.
Alliance Selection:
In alliance selection, we requested Team 449 The Blair Robot Project to LYNK up with us as our first pick, accompanied by Team 1885 Comets. We later LYNKed in 8230 the Koibots as a backup robot. The decision to include Team 8230 was influenced by their swerve capabilities and effective defensive maneuvers, enhancing our alliance’s strategic versatility and we also brought them in so that all the teams at the event got the chance to play in playoffs.
During the lunch break, we crafted a robust strategy with our alliance partners, outlining backup plans and thoroughly discussing the desired approach for each match.
As the top-ranked alliance, we commenced the playoffs on the advantageous red side, offering a clear view of the scoreboard and other game features displayed on the screen behind us. Our alliance embarked on a winning streak until the semi-finals, where an unfortunate camcoder wire disconnection from the intake resulted in a loss with a score of 60 to 85.
Despite this setback, our pit team quickly addressed the issue by securing the disconnected wires, allowing us to bounce back. Navigating through the lower bracket, we fought our way to the finals, delivering impressive scores of 76 and 74 points in consecutive matches. These victories secured the blue banner for our alliance, rookie team, and rookie drive team, marking a monumental achievement at our inaugural event.
It is important to note that by the end of this event, everyone was getting worn out - from the bots to the students - we had just played 16 qual matches and multiple playoff matches. This had been a grueling schedule to maintain, at this later point in the competition this was yet another place where having a relatively simple bot shined and for the most part we were able to keep everything running at tip-top shape.
A couple of key aspects that we identified as strengths and aim to further improve for future events are worth mentioning. Firstly, our team implemented a meticulous Google Forms checklist, diligently followed by our pit crew each time the robot was brought in after a match. This comprehensive checklist enabled us to catch potential issues such as loose bolts, disconnected wires, or wheels entangled with carpet fibers before they became a compounded issue. We strongly believe that this proactive approach significantly contributed to our ability to deliver consistent performance in almost every match, ensuring that our robot operated at its peak throughout the event. This practice not only enhanced our overall gameplay but also instilled a sense of confidence in our team’s ability to tackle challenges effectively.
VABLA was an amazing event, all the teams were incredibly inviting and it was an incredible atmosphere to compete in. We had so much fun competing in the CHS and all the volunteers and coordinators made it a top-notch event to attend!
Socials
This seems a little entitled. Teams do open blogs because they want to help others, and they shouldnt be expected to provide everything immediately.
4481, another team who only releases cad in the offseason has one of the best build blogs. Period. You should read about their philosphy of why here.
Another team, 3255 just released their cad. Stellar team with a stellar blog that has inspired many teams, including my own, with their prototypes. We didn’t need their cad to take their idea and run with it.
Open content teams help the community. Don’t push them away by being greedy.
To 9496, love the work you’ve done, stellar team. Keep it up.
What the hell, child
It looks like they are providing open code with the github link in the original post, so this is still following the guidelines. (Note that I did not actually open the link since I’m on my phone at the moment)
could not have put it better myself
people like you are why teams don’t put OA in my post title nor join OA officially. if teams don’t do open content next year, DMs like yours will be the reason why.
Open Alliance now includes something like 125 teams who do what they can, to varying degrees, and with good intentions across the board but a lot of different interpretations of what it means. If you want to criticize anyone criticize my team, we abruptly stopped posting in February I think, after a couple seasons being prominently featured. We stopped for a lot of reasons, like focusing on internal problems and health issues, but also because we didn’t see a lot of value in what we were doing, it felt like static that just added to the noise of too many weekly blogs about what we built or tested. OA has been and can be helpful, but it has issues and dogging on a team because they didn’t meet your personal standards is a great way to get more of us to drop out of the concept altogether.
Yikes I’m very sorry that my post is having this effect. I can delete it if folks would appreciate that.
At least they have a post, when did yours last update?
I think the spirit of OA is still open here and in yours, but I feel that the rules are more suggestions more than anything.
A: they do
B: this kind of behavior from the community they are trying to help is what pushes teams either away from open alliance or open content as a whole.
This isnt meant to be directed only at you, as I have seen many other people in the community do the same thing. People need to understand Open Content teams help us all, and they need to be grateful for that.
Lucien,
OA is hard - you know this from how hard you worked on ours last year. You can imagine how hard it is for a rookie team with one experienced student.
9496 - keep up with building great robots and posting about it, I hope to see more next year!
I don’t think this response was that bad, the wording was not ideal lol. However, I think OA is hard, and on open alliance or not I don’t think anyone is really in a place to tell a team what they should do (within reason obviously). I think suggestions are good and if you phrased it in a more evidently GP way this wasn’t terrible. And for all those mad at this, I don’t think the intention was bad, everyone in FIRST is learning, even alum.
And congrats to 9496 this season wow, what an incredible bot I love the simplicity.
Congrats on an Incredible Rookie Season! The simplicity of this robot is insane.
This Intake wedge is cool. What material is it?
It’s 3D-printed with PLA. We considered making it with polycarbonate, but PLA worked really well.
Very impressive performance on Archimedes. We watched your robot with interest all weekend (and saw your alliance as a strong challenge in our opening match. The refs helped us.)
Thanks for the kind words, it was amazing to get to compete against a top tier team like yourself. Hopefully we will get to play with y’all in a match one day not just against.
Hey guys! Long time since we have posted, it has been an INSANE season for us, and OA got put on the backburner for a while. The original reason why we signed up to be an OA team was to show future rookies how an FRC season goes and what to expect. As we move forward we will be posting the OA posts drafted after each event (we just didn’t finalize them because we are a small team with little room to spare) but we will get them up soon and we will be moving into what we are doing in our very active off-season.