|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||
|
|||
|
Re: Disappointment (long)
You can't guarantee outcomes -- only effort. If your team did its best, be satisfied. That some other teams had "better" outcomes is just an indication that your hard work should be directed in a slightly different direction next time.
Last edited by Rick TYler : 12-03-2006 at 23:13. |
|
#17
|
||||
|
||||
|
Re: Disappointment (long)
If a person goes gambling (gaming) for the first time and wins a lot of money, they are in real danger of becoming addicted to gambling (it was so easy - I won the first time I played....)
In a way this has happened to you. Its rare for a rookie team to win a regional. Its an outstanding accomplishment when you do, but as they say in the music industry you 'havent paid your dues yet'. There are 6 teams on the field in each game - your team only makes up 16% of the match. No matter how good your robot is it ALWAYS take a bit of luck to come out as the winner of a regional. You need to let that sink in a bit. Winning last year did not happen because you have the best students/mentors/sponsors/school... at the regional. The point is, whether you win is not 100% under your control. So if you win dont let it go to your head, and if you lose dont let it get you down. The robots and the playfield and the plastic trophies <= thats only a game. What you experience along the way <= thats real! No one can take your FIRST experience away from you. |
|
#18
|
|||||
|
|||||
|
Re: Disappointment (long)
Several very experienced folks have already contributed to this thread, so I will limit my own response accordingly.
Team 1625 should be extremely proud of their performance and competitiveness at the 2006 St. Louis Regional. All of their students and mentors that I met conducted themselves as gracious professionals. And their robot was clearly well designed and well built, based both on detailed inspection and, more significantly, on performance in competition. Their performance was also recognized by the Autodesk Visualization Award and the Delphi Driving Tomorrow's Technology Award. There were some complaints about their shooter's muzzle velocity; on two (maybe three?) occasions the head referee ordered ball speed tests. As lead robot inspector the task fell to me to ensure (using the FIRST-supplied ball speedometer device) that 1625 was complying with the muzzle velocity rule <S02> and it is the consensus of all St. Louis officials that they were. I believe the complaints stemmed mainly from competitive envy -- their shooter was easily the most effective at the regional. On behalf of the St. Louis Regional and of my team (931) I want to congratulate 1625, and to repeat what I told many of them personally yesterday -- we would love to see you again in St. Louis every year. |
|
#19
|
||||
|
||||
|
Re: Disappointment (long)
It seems that many of you guys are getting the wrong idea about my post. I do not intend to whine about the outcome of the regional. What is done is done. Take a close look at this.
Quote:
We are already brainstorming ideas of how to make an even better bot. We have continued to learn from our experiences. For example we found out that only one autonomous mode was not enough. We need to be more flexible. We are by no means "giving up" |
|
#20
|
||||
|
||||
|
Re: Disappointment (long)
Quote:
over" but rather as strategies to stop teams from scoring. This game is rough, and honestly, I think it was 100% intended to be played out the way we've seen it. Why on earth would first totally recommend, as said earlier, bumpers. These are just my $0.02, as that's the way I see this game being played. |
|
#21
|
|||||
|
|||||
|
Re: Disappointment (long)
I have never been to a competition before the Arizona regional, and the interaction between robots was pretty much what I expected to see. Aim High is as much a wrestling match as it is a ball game....
|
|
#22
|
||||
|
||||
|
Re: Disappointment (long)
Quote:
|
|
#23
|
||||
|
||||
|
Re: Disappointment (long)
I'm going to play Devil's Advocate here for a moment. When an allaince is playing defense the robots that they are controlling are on the opposite end of the field, and as such they can't always see what's happening...especially if they have 5 other robots running around the field blocking their line of sight.
So granted some tipping may look a little suspicious, but in actuality the driver might not know they have another team wobbly on the ramp. And it would foolish for a driver to stop playing defense because they can't see 100% of what's happening. They owe it to their teammates, their allaince partners, and most importantly themselves to go out on the field and give it their all. If that means that they have to play hard defense in order to win, that's what they're going to do. |
|
#24
|
||||
|
||||
|
Re: Disappointment (long)
Quote:
First i feel for you. I felt great about our robot this year, Atlanta would be nice, but i was just hoping to get into the playoffs. At buckeye we were hit with hardware problem after hardware problem that ended up making us have no auto mode and no camera aiming. But our drive team did a kickbutt job, and even with all the problems we ended the day with a 5-6-0, sitting in 25th spot and with what we felt was an impressive show of our robots abilities, great defense and a good shooter, even if we were getting pushed around a bit. We didn't get picked during alliance selection. i couldn't believe it, since we played well, just had some problematic alliances. 2 lower seed teams got picked over us. Was i disappointed? Yes, i went back down to the pit and just looked at our robot wondering what we had missed. I wanted so badly to get out there one more time just so the rest of the team could go out there to the sideline and cheer there heart out one more time. But this is the nature of FIRST, In games like this defenses is key. Will team 1278 ever build a pure defense bot? i sure hope not, because there is no fun in that. Half the fun in first is taking the hardest goal of the game and trying your hardest to do it. But FIRST is not about having every team build a robot capable of the hardest task, and defense will always play a key role. |
|
#25
|
||||
|
||||
|
Re: Disappointment (long)
the proof of a design is in its performance. If you push a robot by its bumper zone, and it tips over, then it IS a tippy robot.
if the other teams had arms that came out and pushed above the bumper zone, then they are breaking the rules. If a team pushes a robot and it keeps tipping over, what is the logical conclusion? That robot should be allowed to sit infront of the goal and shoot all day long, untouched? or that team should find a way to stop its bot from tipping over so much (modify the robot)? This is part of the 'paying your dues' that I was talking about. You had a notion of how the game would be played this year, and its a bit rougher on the field than you expected. The refs did not call any fouls, therefore what you saw IS the game this year. now its up to you: will you modify your understanding of how the game is be played (this year and in the following years), or will you hang onto your previous notions of how you think the game should have been played, and in the process conclude that FIRST is screwed up? Last edited by KenWittlief : 12-03-2006 at 15:36. |
|
#26
|
|||
|
|||
|
Re: Disappointment (long)
I can understand well the highs and the lows of competition, just as you describe them, Chris27. I am the parent mentor of a team. I think all teams go through the process you describe at one time or another. Our team has been through a couple of rough years in transition from one major sponsor to another. Many teams are in the same boat. We played in our one and only compeition this year and we didn't make it to the finals, BUT we were winners. After our major sponsor pulled out on September 23 we had no money. Most of our team quit, but the 3 remaining players worked their buns off fundraising and with the gracious help of other teams and some nice people, we were able to register. 2 weeks into the build season is when we found an engineer and simultaneously got a check that allowed us to buy parts. Our kids worked hard, too. They were there every day after school. There was only 3 or 4 kids and the engineer, but they did it. They built a robot and I am proud to say that our kids did all the work. Our engineer took their design and he did alot of the cutting and machining, but our kids designed the robot and they put it together and tested it. It might not have been the best or the most pleasing to the eye, but they got it done and they competed well. They really came together as a team, supporting each other and they placed in the top 20 of the 63 robots in our regional. The scoring was messed up for the first 14 matches of our regional and that messed everyone up, but the point it that we made it there, we learned a ton, and we overcame adversity through sheer tenacity and by the gracious professionalism of other teams that helped us along the way. I am so proud of our kids and I hope they are, too. That is what FIRST is all about. Disappointment is a part of it, but overcoming that moment of regret and seeing pride in all you've accomplished will help you to look forward to next year with excitement and anticipation. I would encourage you to try another regional. If for no other reason, than to get to meet other teams and people and see a new place. Good Luck!
|
|
#27
|
||||
|
||||
|
Re: Disappointment (long)
If I can get a hold on some of the video we took I will post it. It should reveal more about the intentions of the opposing team. And btw you can tip over any robot no matter how well it is designed.
|
|
#28
|
||||
|
||||
|
Re: Disappointment (long)
Quote:
I'm gonna have to argue with you there...especially now since there's a rule (forgive me, I forget the rule number) where all sides of a robot MUST be within 10 degrees of vertical. So this year it's essentially a flat face pushing against a flat face. Unlike in years past where teams used wedges for defense (although some teams used them for offense) they would sit there and score with no worries about being pushed due to the fact that if another team tried to push them they would ride up on the wedge. I digress, at NJ the most dominant team, IMO, was 25. if I remember correctly I only saw them twice (and I saw every match since I was Game Announcer) the two times they tipped were from getting caught on a ball going up the ramp, and going forward on the ramp and going backward very quickly which tipped them over. They were being shoved around ALL REGIONAL LONG, and no robot was able to tip them. Add to that that they had one of the lowest shooters in the game, and they managed to come away as #1 seed and eventual Regional Champions is just a testament to the design of their robot, and their ability to adapt. |
|
#29
|
|||
|
|||
|
Re: Disappointment (long)
Hey 1625. I havent read the whole thread but you guys had an awesome bot. We really wanted to be on your alliance for finals but we were picked one team ahead of you. I was dissappointed that you guys didnt make it to the finals because we were really looking forward to your excellant competition.
|
|
#30
|
|||
|
|||
|
Re: Disappointment (long)
Quote:
We ended up being a strong defensive force even though we intended to be a top shooter. The only thing separating good defenders from poor ones is the drivetrain and chassis. In the matches I saw, nearly all of the robots that tipped over had top-heavy designs. Most would tip themselves over just driving up the ramp at anything other than an optimal angle. Those of you who feel like you were tipped over unfairly can usually look at your design for the reason. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Accelerometer code | ImmortalAres | Programming | 28 | 04-06-2005 01:02 |
| Threads getting too long to make sense of | Ken Leung | CD Forum Support | 22 | 05-05-2005 01:14 |
| Northrop/FIRST | Redhead Jokes | General Forum | 9 | 20-09-2004 12:24 |
| How long should production time be??? | archiver | 1999 | 4 | 23-06-2002 23:16 |