Feb 20, 2018 11:59 PM:
Mar 1, 2018 8:00 AM:
Central NY Regional
Full event list
FIRST® Things FirstWhat is FIRST?
FIRST Official Site
FIRST in the News
FRC® Game Details
FRC® Game Animations
MultimediaFIRST Promo Videos
FIRST News Segments
Team 358 Photos & Videos
Team ResourcesStart a Team
Technical ResourcesControl System
General ResourcesOffsite Resources
Long Island Teams
FIRST® Robotics Competition (FRC®)
History Main | 2000: CO-OPERTITION FIRST | 2001: DIABOLICAL DYNAMICS | 2002: ZONE ZEAL | 2003: STACK ATTACK | 2004: FIRST FRENZY - RAISING THE BAR | 2005: TRIPLE PLAY | 2006: AIM HIGH | 2007: RACK 'N' ROLL | 2008: OVERDRIVE | 2009: LUNACY® | 2010: BREAKAWAY | 2011: LOGOMOTION | 2012: REBOUND Rumble | 2013: ULTIMATE ASCENT | 2014: AERIAL ASSIST | 2015: Recycle Rush | 2016: Stronghold | 2017: Steamworks | 2018: POWERUP
2002: ZONE ZEAL
ChiefDelphi Forums (http://www.chiefdelphi.com/forums/index.php)
- General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
- - IS THIS RIGHT?!?!? (http://www.chiefdelphi.com/forums/showthread.php?t=3087)
RebAl 03-17-2002 09:53 AM (Student on Team 329 owner of the MouseBot)
IS THIS RIGHT?!?!?
We just completed the SBPLI Regional and it was great. Had it not been for one disturbing event, it would have been awesome. Very briefly, here's what occurred.
On Thursday during pit day we were besieged with inspectors (at least 5) wanting to see our mouse's tether. They said that other teams were complaining that it was an entangling threat. I thought that to be ironic since the mouse itself could easily drive over it with no problem. We took it in stride and were granted permission to proceed.
It is a 6 lb, 6 ft./sec. agile mouse with a 42' tether. During 9 of the 10 matches we used it and kept it out of all other robots' way. We went end zone to end zone several times. In our last qualifying round however, we accidentally released it too early and couldn't rehouse it. To keep it out of the way we ran it into our opponent’s end zone and rested it against their wall. Soon after, one of their teams drove a goal out of scoring position and ran it into the mouse, crushing it. Had it been to merely move the goal out of scoring position I could have accepted the consequences. But the team kept pushing the 180 lb. goal against the 6 lb. mouse to ensure its demise. After the round the refs. refused to DQ the intentional action even after a crewmember said that he clearly heard the operators laughing that they finally "Crushed that little thing". He said that he couldn't know their what their intention was and that they might not have been able to see what was happening. They kept pushing the robot into the wall, AND it was against the wall right in front of them!!! Not to mention on the big screen at the time for all to see (across the field from them so they could see it).
Okay, I'll accept that, after all we have to make it robust enough (I defy someone to crush the one we'll have in the Nats.) What is really disturbing though is the very ambiguous message FIRST is sending this year.
At the close of rounds on Fri. we were seeded 5th and received the Xerox Award for "Thinking outside the box" with the design of our mouse and heads up LED goggles. The four students who designed and built the mouse, including the programming, were very excited and proud of their achievement.
At the end of the competition on Sat., however, they were ready to give the award back because it meant very little to them. You see, the team who crushed the mouse was given The Best Defensive Play Award for crushing the mouse in a "Mouse Trap". Now, explain how, on one hand it was completely unintentional that they damaged the mouse and were merely trying to move the goal into the non-scoring zone yet at the same time you REWARD them for damaging the mouse by intentionally stopping it. I would be like giving out a award last year to a team who snapped off a arm off a big ball getter and were not punished right off for it. Whats the diffrence between a mouse and say bashing off a goal grabber on another robot while having you wheels spinning, just because you could. Professional graciousness?
Yes, I know that the Best Defensive Play is voted on by other teams- then shame on them. This only shows that FIRST is missing the mark and fomenting a Battlebot mentality when some teams praise others who damage robots. I found it odd that teams who allied with us and won, loved the little guy and even respected it when they later opposed it. Yet teams who only faced us as an opponent were stymied, frustrated even angry because they couldn’t stop it.
To add insult to injury the judges themselves nest awarded the same team another award in which they remarked about the stopping of the mouse. FIRST needs to stop worrying about exciting the spectators and keep worrying about exciting the students; ours walked out of the competition after those awards were given.
Is this sour grapes? No, we went and rebuilt the mouse and competed in the next round as a non-scoring partner (To round out match numbers) and won because of the mouse.
Another team’s advisor compared the stopping of the mouse to the breaking of a star quarterbacks legs to get him off the field.
Sorry for venting here, but I truly pity the other mouse teams who have yet to compete for the first time this year; Good Luck
Ken358 03-17-2002 04:45 PM (Adult leader and field coach of Team 358)
Response to “Is This Right”,
I would like to start by formally apologizing for any damage that the “mouse” may have sustained. It was definitely not our intention to cause any damage. Many of our team members commented on what a great idea the mouse was as they scouted in the pits. We were not one of the teams who brought up the entanglement issue.
If you saw our robot you would know that it was designed with defense in mind. Our game plan was basically to defend our goal zone in an effort to keep the opposing teams goals from scoring. We rarely even crossed the middle of the field. Our cross axis drive train allows driving back and forth sideways in the goal zone. Many of the robots at the competition had much more aggressive designs. The play in question was also essentially a defensive play. We did not win the “best play award” for damaging the mouse. We won the award for quickly reversing what appeared to be a hopeless losing match. With very little time left, we managed to escape one opposing robot that had intentionally lifted us off our wheels and pinned us against a goal. Then we raced across the field, pushed the opposing teams goal out of the scoring zone into our home zone (that is the defensive part). We also got our robot into our home zone while blocking the mouse from escaping, thus insuring us the win.
It just so happened that the mouse was lined up with the goal in such a way that when we came roaring into the home zone pushing the goal, the goal struck the mouse. In the time we had to get the goal out of the scoring zone and to get our robot into the home zone, there is no way we could have taken the time to steer into the mouse. We just gave the goal a high-speed push in a straight line. Unfortunately for the mouse it was in the path of the goal. Our drivers couldn’t even see the mouse from their position in the driver’s station since the mouse was up against the wall. The only way to know the position of the mouse was by inferring its position by looking at the tether. Our drivers are good, but to steer a 180-pound goal with a 127-pound robot that does not physically couple to the goal is a near impossibility when considering the time frame of a few seconds. As for the big screen, it is very hard to drive your robot while looking at the big screen. When you are driving you are singly focused on watching your bot not the screen. The camera angle on the screen is always changing so you cannot drive using the big screen as a monitor.
I have also heard that some believe that we went into the match with the sole purpose of destroying the mouse. How could we plan the chain of events that led to the mouse’s destruction? Our team is not that good. The only reason that the mouse was in our home zone in the first place is that we were losing so badly that team 329 drove their mouse to our side so that they could maximize their points. Did we some how plan this??? Did we start losing so badly to lure the mouse over to our side of the field???? If the game had played out with the mouse running back to the opponent’s home zone as is conventionally the case we never would have come in contact with it. (Our robot rarely crosses the entire field.) Are these the same people who believe that the moon landing was one big conspiracy???????
After the incident the driver asked me (teacher/mentor) to go with him to apologize for damaging the robot. When we went over everyone was understandably feverishly working. We got the ear of one student and he graciously accepted the apology. He did say that he was disappointed and believed that we continued pushing the goal longer than necessary. (He said he saw our wheels spinning) Maybe, maybe not. Our robot is only 1.5 inches off the ground. It is very hard to slow down and stop instantly from full speed. We have all seen major league baseball players run into the wall after making a catch. (Because he couldn’t slow down in time) What was most disconcerting was what he said next. He pointed to an adult member of the team and said. “Don’t let that guy see you, he wants to kill you.” (Figuratively I am sure) I can understand that this adult was upset, but usually in FIRST any misunderstanding is between the students. We left the pit and went back to our own not wanting to cause any kind of confrontation and to let all parties involved calm down.
We do not come to FIRST events looking to damage anyone. We are always willing to lend tools and support to anyone who wants it. We are not involved in FIRST with a sole aim of winning events or awards. We do it because it offers our students with a unique experience that combines competition with caring and giving. Since we are not there for cutthroat competitiveness, I hardly see how the quarterback analogy fits this situation. We had no way of knowing if team 329 would be an alliance partner in the future so why would we want to render them useless?
The award was based on voting from other teams at the event. So clearly the overwhelming majority of those who witnessed the match saw it differently than 329. Most of the responses on this board so far have been from people who did not actually see it. Please respond if you saw the event. We would like to hear your perspective. On one point we can agree, overall the event was a huge success and everyone had a great time. Thanks to everyone who worked tirelessly to make this event a success. (Especially Fred) See you in NYC. I hope no one has gotten the wrong impression of our team. Our drivers were very concerned when they first heard the accusations.
Hauppauge Team 358
Jason Haaga 03-17-2002 07:52 PM (Student from Team 173 an uninvolved spectator)
I agree the lil extra push was probably not in good taste, but it didn't really matter. The mouse was crushed like a tin can practically on impact from my viewing angle. Also, it is pretty tough to see around those goals when you're moving around so I'd give the drivers (who from experience are nice people) the benefit of the doubt in their intentions. Personally I can't wait to see the mouse souped up at Nats. It's a great idea, and from what I saw at LI it works really well.
Kevin Ray 03-17-2002 09:19 PM (Adult leader of Team 329 owner of the MouseBot)
Ken358 thank you for your lucid explanation of your team’s view of the incidents involved (The actual round and the award determination). I graciously accept your apology and am sure that most, if not all of our team members will do the same after reading your post. I don’t want there ever to be any hard feelings that might stand in the way of the success of this program.
For those readers who are not familiar with team 358, they are sponsored by FESTO, a major contributor to the FIRST program and sponsors of several other teams in some capacity or another. They also have run numerous workshops to help teams better understand the function and operation of pneumatics. Every person associated with the team that I’ve ever met including coaches, advisors and engineers were outstanding individuals. In fact, two rounds prior to the incident with the mouse, one of their engineers came to our assistance to help us with a pneumatic problem at a moments notice. I am completely sure that they have never entered a match with the intention of harming or destroying any robot or part thereof. I feel that the problem lies with the message that FIRST is allowing to be sent, no matter how overt or innocuous it may be.
I can understand, in the heat of the moment, any student getting excited or even happy about the events of the round that enabled them to win. I don’t wish to argue whether or not actions were taken or that things were said by students after the mouse’s demise; in the heat of the moment we all can say regrettable things. In fact, I wasn’t too bothered by the actual damage to the mouse and even stated that it could happen in a thread prior to the whole regional competition. I WAS upset by the way that FIRST handled the matter. I know that the teams voted on the award, but it was the FIRST judges with the approval of FIRST staff members who used the definitive phrase “Mouse Trap” (Sorry Ken, but that is what the text said you were being given the award for). I feel that there are times when the FIRST staff needs to usurp the decision of the voters when it is not in the best interest of the program and choose the defensive move which received the second greatest number of votes. Like maybe, Team 28 who, without an ally even showing up for the round, went end zone to end zone twice to beat two powerful opponents single handedly!!!! I say this not to keep the award from a very good team like 358, but rather not to foster the idea that damaging robots is something we want to do. Heck, they could even have still given the award to them for that round and mentioned everything that they did which deserved the award---but don’t SMILE when you read the phrase MOUSE TRAP.
I feel like this year we’ve moved two large steps closer to Battlebot mentality to gain a greater “share of the viewing audience”. And it was done at the expense of the basic precepts of the FIRST program. If we really want to encourage students to develop innovative designs and enjoy working with professionals in the engineering field we won’t do it if all they talk about when the return to the pits is how their next robot is going to be a “KILLERBOT”.
Again, please understand that any misunderstanding that might have existed were probably due to “the heat of the moment” and that we harbor no ill feelings, we just want future matches to engender all the goals of the FIRST spirit.
Teddy358 03-18-2002 02:09 PM (Driver of Team 358)
Re: Is This Right?!?!?
I really want to clear everything up here and now. I was driving for team 358 in the round you are referring to and there was nothing planned about destroying the mouse. We were paired with team 56, who can grab 2 goals and load them with balls and has a very good braking system. We (team 358) are mainly a defensive robot with a pusher arm and cross axis drive system, which seconds as a brake. We were against team 514 who can grab 1 goal and has a lifting arm, which is a very powerful robot, and team 329, the team with the mouse. Our strategy (358 and 56) was for team 56 to go out and immediately load up on balls. While that was going on 358 was going to help by pushing a goal past all the balls and guarding it for 56 to grab load up with balls and plant in the goal zone. Then 358 was supposed to go back and push 514 into our home robot zone along with a goal that they hoped they were going to be guarding or just a free goal out of the other teams goal zone taking 10 points away from them. Then hopefully 329 would be holding a goal in the goal zone for them and be letting the mouse back into their own home robot zone like they usually do. We (358 and 56) were going to leave 329 alone to do their thing b/c we wanted the mouse to go back to their home zone. That plan would have given 358 and 56 a 36-30 win. But because nothing ever goes as planned, 358 was being lifted up by 514. Because I (the driver for 358) thought that was considered a pin I was waiting for the refs to give the 10 count and for 514 to have to put 358 down (After the match we found out that lifting a robot is legal but because they didn’t have us against the railing, a wall, a goal or another robot we were not pinned). During that time I believe 329 was being smart and saw that since they were winning by a lot and they thought that 358 wasn’t going to be able to get down and get back into their home robot zone for 10 points they sent the mouse out into our home robot zone to maximize their Qualifying Points. While this was going on I was trying to get our team’s robot free and back into our home robot zone. On the way back to the home robot zone I saw that the other team had a goal full of balls in their goal zone so getting back to the plan I pushed it out of the goal zone and into the robot zone with our robot moving it out of scoring position. Unfortunately the mouse was in the line of fire and it was truly an accident that it was damaged.
About the comment “They kept pushing the robot into the wall, AND it was against the wall right in front of them!!! Not to mention on the big screen at the time for all to see (across the field from them so they could see it)”. First, I did not continue to push the goal into the wall after it hit the wall, Second, anyone that has been behind the glass there knows that if there is something small, such as the other teams mouse, against the wall it cannot be seen by the people behind the glass and Third, whoever is driving doesn’t look up at the big screen to see what is going on during a match, I am usually looking directly on the field to see where I am driving our robot.
It was truly an unfortunate accident.
And about the comment “a crewmember said that he clearly heard the operators laughing that they finally "Crushed that little thing".” When I pushed the goal out of the goal zone I didn’t realize all the cheering was because the mouse got crushed and not b/c I pushed the goal out of the goal zone until way after the match. I was just excited b/c we won the match, I didn’t even know that the mouse got crushed. But as to my teammates comment, I do agree was inappropriate but everybody including the audience was caught up in the moment.
I hope this clears everything up Teddy Melnick Team 358
Elgin Clock 03-18-2002 05:18 PM (Unrelated team 237, not at the Long Island regional)
I have two points to make.
First I am truly sorry for what happened no matter what the circumstances, intentional or unintentional destruction. It's always sad to see a robot be destroyed while in the heat of the moment on the field.
Why are these judges even allowing these "go home devices" on the field??? In the FRCTech on yahoo groups in the beginning of the year during build season there were comments that if ANYTHING that was on your robot that can cause an entanglement issue you would be DQ'ed. Now what do I see when I watch the webcasts and the NASA tv regionals, but all these "mice, mini me's send home devices" what ever you want to call them all over the field. I believe that these devices SHOULD NOT be allowed to continue to operate in this game. They are all possible entanglement issues and should be immediatley banned. One match I saw on NASA tv Saturday had one of these "parasites" that released itself from it's "host" robot and proceeded to make it's way to the other end of the field and while doing so it didn't allow any robots on the other alliance to pass over it's cord. I think the drivers of the opposite alliance just did not want to wreck the device by driving over it but it left them sitting there on one side of the field in a disadvantaged position. I applaud that alliances gracious professionalism in that respect but because of that disadvantage, they lost the match.
All you teams out there with these "parasites" just better be greatful that I am not a driver. Because as you could probably deduce, If I were a driver, your "parasite" would not stop me from crossing the field, it would get run over and possibly destroyed! That is the chance you are all going to take I assume?? If so, I don't like your odds!
Kevin Ray 03-18-2002 08:45 PM (Adult leader of Team 329 owner of the MouseBot)
Re:Elgin Clock rsponse above
Hmmmmm, Did someone miss their Battlebot counseling session? Have you been reading any of this thread, or are you just another disgruntled, anti-mouse team member who wants to have a forum for that view.
WHAT IS THE PROBLEM WITH A TEAM HAVING A MOUSE????? And please stop crying about the entanglement issue (The only argument you have), because in our 13 rounds no one got entangled, in fact, the little mouse even drove over its own tether without getting entangled. Now I'm sure that with your big bad robot who is willing to "run over it", you too can get around without getting entangled. It seems that those who have a violent opposition to a mouse have other issues they need to deal with.
BTW-- Teddy Melnick team 358, Thank you for the explanation. I'm sorry if you've been taking any heat, I honestly am. I think that you make very valid points and we are not at all upset now. Please, let's put this to rest.
Note: Some responses have been removed as distracting from the core comments in this thread. For the full text see: http://www.chiefdelphi.com/forums/showthread.php?t=3087