Indiana Rookies! (far from it!)

[Chris Fultz]

Congratulations to all of the rookie teams that competed at Boilermaker this weekend. There were 10 new teams there - 9 from Indiana and 1 from Ohio (25% of the field).

All of these teams played well and had robots on the field almost every match. 2 were finalists and played very well to get there!

Many got to this point with the help of other veteran teams during build season and at the event. Everyone should be proud!

This is what it is all about. !

[deadman666]

yes i thought that too.
i was surpried with how many there were and how well they did.
Sadly i was one of the team members (3487) that lost to them because of a bad call but hey life goes on

[IndySam]

Originally Posted by deadman666

yes i thought that too.
i was surpried with how many there were and how well they did.
Sadly i was one of the team members (3487) that lost to them because of a bad call but hey life goes on

Bad call, please elaborate?

[deadman666]

Your team was part of our alliance for the simi finals team 234 cyber blue right? Anyway we were backed up against the bump by the goals and were ran into to aggresevly (sorry for my bad spelling) by our count three times by a rookie team (i think 3947 lost raiders?) and they caused an electrical blowout on our c-reio. We have a few vidios of the match and you can count how many they hit us. The alliance was flagged for that when it should have been the blue alliance.

[Ben Martin]

The rookie talent at Purdue was tremendous. I had a discussion with several Purdue FIRST members Friday night about how team age seemed to not be a factor for team field success at BMR.

At Purdue, we are especially proud of our newest Purdue FIRST team, 4272. The students on the team put forth enormous effort to field a robot that experienced few technical issues throughout the competition and seeded higher than any of the three other PFP teams. Good job captaining the 8th seed alliance to the semifinals.

Congratulations to 4028 on winning a competition in your rookie year, as that is no easy feat.

Aside from the 4-award sweep by 1501 (congratulations on your first regional win by the way, well deserved) and the 3-award sweep by 1732 (congratulations on the RCA, also well deserved), no other teams were as successful as 3940 and 3947. A big congratulations to both of you.

[sprocketman92]

I am sorry that you feel that it was a bad call but may i remind you that the earthquakers (3487) robot was on the blue side of the field and you were on our fender in which you were playing defense on 3947 (THE LAST CRUSADERS) which is fine you can play defense but since you were on the opposite alliances side of the field the contact was not a foul. If you are talking about the "intensity" of the impacts I think you should refer to [G27]


[G27]
Deliberate or damaging contact with an opponent Robot on or inside its Frame Perimeter is not allowed.
Violation: Technical-Foul and potential Yellow Card


High speed accidental collisions may occur during the Match and are an expected part of the game. Robots place mechanisms outside of the Frame Perimeter at their own risk; no penalties will be assigned for contact between two such extended mechanisms.

A Robot with a mechanism outside of its Frame Perimeter may be penalized under this rule if it appears they are using that mechanism to purposefully contact another Robot inside its Frame Perimeter. Regardless of intent, a Robot with a mechanism outside its Frame Perimeter that causes damage to another Robot inside of its Frame Perimeter will be penalized.

Repeated or egregious violations of this rule will earn the offending Robot a Yellow Card.

Since I am one of the drivers i can tell you that we were just trying to get to the basket as fast as we could so we could score since you guys were playing such good defense and you guys stopped us before we even got to the baskets therefore impact occurred. We are sorry that your robot was damaged but we feel that the referees did a great job and it wasn't a bad call.

[sprocketman92]

Thank you Chris we had a lot of fun competing against you and The Whole Cyber Blue team your whole alliance was tough thanks for the fun competition

[Duke461]

Originally Posted by sprocketman92

I am sorry that you feel that it was a bad call but may i remind you that the earthquakers (3487) robot was on the blue side of the field and you were on our fender in which you were playing defense on 3947 (THE LAST CRUSADERS) which is fine you can play defense but since you were on the opposite alliances side of the field the contact was not a foul. If you are talking about the "intensity" of the impacts I think you should refer to [G27]


[G27]
Deliberate or damaging contact with an opponent Robot on or inside its Frame Perimeter is not allowed.
Violation: Technical-Foul and potential Yellow Card


High speed accidental collisions may occur during the Match and are an expected part of the game. Robots place mechanisms outside of the Frame Perimeter at their own risk; no penalties will be assigned for contact between two such extended mechanisms.

A Robot with a mechanism outside of its Frame Perimeter may be penalized under this rule if it appears they are using that mechanism to purposefully contact another Robot inside its Frame Perimeter. Regardless of intent, a Robot with a mechanism outside its Frame Perimeter that causes damage to another Robot inside of its Frame Perimeter will be penalized.

Repeated or egregious violations of this rule will earn the offending Robot a Yellow Card.

Since I am one of the drivers i can tell you that we were just trying to get to the basket as fast as we could so we could score since you guys were playing such good defense and you guys stopped us before we even got to the baskets therefore impact occurred. We are sorry that your robot was damaged but we feel that the referees did a great job and it wasn't a bad call.

Being out there and on 3487's alliance, i have to say i didn't feel it was egregious. The real problem i have is the Field guys not letting them have another 10 seconds to finish deploying their code, when the match didnt even start for another minute.
But, this is not a thread for complaining. This is a thread to praise the rookies. You all did fantastic and should be very proud.
-Duke

[ratdude747]

I agree, there was a lot of rookie talent at BMR this year. In many cases the only way a rookie could be identified was by the number... I was very impressed.

Hopefully BMR next year will be just as good if not better...

[travisc94]

Originally Posted by sprocketman92

I am sorry that you feel that it was a bad call but may i remind you that the earthquakers (3487) robot was on the blue side of the field and you were on our fender in which you were playing defense on 3947 (THE LAST CRUSADERS) which is fine you can play defense but since you were on the opposite alliances side of the field the contact was not a foul. If you are talking about the "intensity" of the impacts I think you should refer to [G27]


[G27]
Deliberate or damaging contact with an opponent Robot on or inside its Frame Perimeter is not allowed.
Violation: Technical-Foul and potential Yellow Card


High speed accidental collisions may occur during the Match and are an expected part of the game. Robots place mechanisms outside of the Frame Perimeter at their own risk; no penalties will be assigned for contact between two such extended mechanisms.

A Robot with a mechanism outside of its Frame Perimeter may be penalized under this rule if it appears they are using that mechanism to purposefully contact another Robot inside its Frame Perimeter. Regardless of intent, a Robot with a mechanism outside its Frame Perimeter that causes damage to another Robot inside of its Frame Perimeter will be penalized.

Repeated or egregious violations of this rule will earn the offending Robot a Yellow Card.

Since I am one of the drivers i can tell you that we were just trying to get to the basket as fast as we could so we could score since you guys were playing such good defense and you guys stopped us before we even got to the baskets therefore impact occurred. We are sorry that your robot was damaged but we feel that the referees did a great job and it wasn't a bad call.

Although the rules don't specifically rule out a destruction derby, they do sum that up in the introduction with gracious professionalism. It would be cool for FRC to make a rule against such a thing. Yes high speed collisions are expected and thats part of the game, but moving a robot out of the way by moving perpendicular to a wall actually doesn't move anything out of the way. Moving parallel to the wall to remove a robot from your intended location would have been a cool move instead. The incident may have been percieved as bad by everyone since te strategy ends in destruction. The refs made a good call, as they are following the rules, but FRC should keep this incident in mind for next year.

Otherwise, we could have just had a destruction derby if we followed the rules verbatim.

Anyways, it was great seeing so many new teams. There was a great sense of community and support from everyone and it was a blast helping out other teams.

[travisc94]

Originally Posted by Duke461

Being out there and on 3487's alliance, i have to say i didn't feel it was egregious. The real problem i have is the Field guys not letting them have another 10 seconds to finish deploying their code, when the match didnt even start for another minute.
But, this is not a thread for complaining. This is a thread to praise the rookies. You all did fantastic and should be very proud.
-Duke

FRC is great. If you noticed, we actually got extra time. Everyone stalled for us. The refs checked the hoops to make sure they weren't broken, they even checked the bridges. Unfortunately, we may have had extra time if more teams called timeout, but it was great fun!

[Duke461]

Originally Posted by travisc94

FRC is great. If you noticed, we actually got extra time. Everyone stalled for us. The refs checked the hoops to make sure they weren't broken, they even checked the bridges. Unfortunately, we may have had extra time if more teams called timeout, but it was great fun!

Good point, and i really shouldn't have even made that complaint regardless.

Back to rookies, 4272 is soooo good!

-Duke

[thecrusadergirl]

[/size]Thank you, Chris! I am from team 3947, but I think I speak for all of the rookie teams when I say that we really appreciate your praise! We wouldn't be where we are if it weren't for all of the people that supported us through this, too! [/font]

[deadman666]

Congratulations to all of the rookies that showed up at BMR.

I realy enjoyed watching team 3947 stomp everyone to oblivion.
hope they have fun at Nationals!