We won!
Ladies and gentleman, my team has claimed its first blue banner! Two of our mentors even made a cake to celebrate!
We won!
Ladies and gentleman, my team has claimed its first blue banner! Two of our mentors even made a cake to celebrate!
Hi readers,
First off, I know this title may be a little clickbait. I acknowledged it, so it's not greedy!
Anyways, apparently I am in the top 5% of my graduating class, which consists of about 280 students I think. If you do the math, that means I am one of 14 students.
Now, if you're reading this, you probably know me. And if you know me, you probably know that I'm an idiot who applies himself when interested.
So how did I manage to rise to the top 5%? Dedication. Effort. Focus. Respect. Punctiliousness.
I also feel it's because some of my classes have not been the most challenging. In fact, in my freshman year I took your typical, college-prep classes. Why? I was not as dedicated or as interested in the sciences as I am now. But thanks to robotics and friends, I have changed by ways and look forward to challenge! Especially programming challenges!
For this recognition, I did have to choose a mentor. It doesn't matter what relation you have with the mentor, as long as they influenced your education. So naturally, who better than a robotics mentor? I selected my team's head mentor; let's call him Joe. So Joe has been here about the same length of time I have, and we became very close throughout this experience. My brother and I still learn, build, and even snowmobile with Joe! I could not be more proud of my selection, who also happens to be a frequent reader!
I'll update you guys with my "keys to success" once I develop them.
By the way, still first in our division, but 20th in the world unfortunately (I think I'll live).
I worked my first double shift last Sunday too! Super fun and adrenalizing! I really enjoyed transporting my coworkers, which actually included a team member's sister! But at the end of the day, the radio was the coolest part!
Lastly, I am developing a series of lessons for teaching students who to program on my team. Or, at least how I think programming and the programming department should look. I will share all of this eventually, but I want to finish it first!
I also have some very exciting events approaching, but I will wait to share those until next time!
Once again, thank you for reading!
The Questionable Programmer
Hi all,
I don't want to waste your time so I suppose I'll jump right in. Although this title is partially clickbait, it is still partially true! We did submit all scores last Thursday, and when we did, we were still in first in our group! This is great news, and I really look forward to seeing if win! Technically, we already unofficially won our division, but I need FIRST to say that for it to be true and exciting!
Our division's scores can be found here if you have not seen them yet.
I apologize for not updating on Thursday or Friday, but I think this is close enough!
Thanks for reading,
The Questionable Programmer
Hello readers,
I'd first like to apologize for my disappearance once more; I have been awfully busy with work events as well as robotics of course.
As most of you know, the FRC 2021 season is a little special, to say the least. Rather than hosting the typical build season with in-person events and a World Championship (which we attended in 2019!), they decided to create three different challenges encompassing both those who have access to their robot, and those who don't.
For those who are interested in FRC Game Theory and Design, there was a challenge for that. There was also a product design challenge for team's who are more focused on universal and community impact. More information on these two challenges can be found here.
Personally, I took more interest in the third challenge: the at-home challenges. These were challenges that involved the robot and its capabilities, such as cycle speed, accuracy, driver skill, and autonomous potential.
Long story short, we were randomly assigned a group of 29 teams to compete with, and it seems pretty good. 303, Test Team, was the only team I recognized from the FMA district however; all the others are new to me.
We generally have really strong scores across the five challenges. Not perfect, but good; in fact, maybe good enough to win our group? Maybe. We are interested to see how other teams do, but so far no team has compared to our scores. Until now.
FRC Team 3130 of Minnesota is here with some good scores, and it's rather frightening. We are about even, and I have yet to see them post scores to the two shooting challenges. I need to get the autonomous challenge faster to secure a win however. Nevertheless, there are less than three days of competition left. All scores are due on the eighth by 3 PM Eastern. Tomorrow I plan on speeding up that auto, and taking Wednesday if need be.
Nevertheless, we are going to do the best we can, and if we cannot beat them, too bad so sad. Nothing much we can do about their score. But I remain hopeful. I look forward to updating you all on the eighth.
Small rant time. Skip if you want.
So when I first started the season, I was excited to see FRC's unique take on the 2021 game/games. My opinion of the 2021 season gradually declined however. To be honest, I feel as though it is a lot more tedious and frustrating than a normal season. I also really dislike the way FIRST is handling the scoring. For two of the scores, they state that if you over-score yourselves, accidentally or purposefully, they throw your score out. If you underscore it, they do nothing. It's like The Price is Right. Yet unlike The Price is Right, this infuriates me. I think it's stupid that one small mistake or difference in opinion is a throw-away of what could maybe be the best score ever. It's not like teams would argue; they basically have no valid way of arguing since they have no idea who scored their piece.
Although the Power Port challenge, a challenge which includes 60 seconds of cycling and shooting is exciting, it is, in my opinion, almost ignorant of the robot's skill compared to the skill of the human participants.
By forcing two people to collect the same three balls from either behind the power port or in front of it (depends on which configuration you used), you are testing the robot's aim, and that's about it. Speed of the robot does not play a huge role, but human speed and hand-eye coordination do. FIRST prides itself on offering activities that give the competitiveness of sports, but also the joys of robot skill and performance and not the physical potential of team members. Speed of the robot is typically regardless because humans will usually take longer than the robot. This challenge also frustrates me because the challenge incorporates little of the robot. For us, it was really only the shooter and the aiming components. We didn't need the intake and the climber, and that goes for most challenges to be honest. It was always these systems. I felt disappointed in the challenges we received. To prevent being overly hypocritical, let me lay down a few suggestions: a speed-climbing challenge, an auto challenge which involved shooting, or a color wheel challenge.
Although my proposed challenges present a plethora of difficulties, isn't their job to overcome these? I don't think the challenges are that difficult to implement, and I certainly think they provide a better alternative to the 2020 game people were looking forward to playing. Shooting these yellow dodge balls repeatedly is quite boring, and drivetrain skill is certainly nothing new.
All in all, I feel as though these games are the "tip of the iceberg", and that this season could have been so much more if they put more effort into these at-home challenges.
However, what's in the past is in the past, and I certainly can not change it.
End rant.
In early March, I managed to earn myself a promotion at work. In fact, I am now an assistant supervisor. My tasks are much more different than what they used to be, but they still revolve around the same core concepts: respect, treat guests well, and honor our founder. I look forward to dealing with the Karens and helping out my coworkers across the park! My first day is this Sunday, although it was originally supposed to be the past weekend (one of my close friends and team members got COVID-19 [he will be ok]), so hopefully I can inform you when I also inform you about FRC Team 3130 and our performance. The shift also happens to be a double shift, 0830 - 2100 *excited nerd noises*!
Easter was also yesterday, so it was nice to see most of my family together and healthy too.
I have a lot of stress on my mind with these challenges, so the sooner its over the better I suppose. Just gotta do my best!
Again, sorry for my disappearance; just know that I'm still here, and still coding.
Just kidding! Look here for my most recent work involving Bezier curve generation and following. If you wanna see the inner guts of it, trace it back to the swervedrive.py file in the subsystems folder and locate the methods you are interested in (which is most likely the slope finder of higher degree Bezier curves!) This code certainly lives up to my name of, The Questionable Programmer.
And with that ladies and gentlemen, I bring this to a close. Thanks for sticking with me once again, and I look forward to writing to you all very soon.
Sincerely,
The Questionable Programmer
Hi everyone, I know it's been a while since my last post, but I am certainly in a much better mindset now! Blogging, firefighting, and ...