Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Extra Discussion (http://www.chiefdelphi.com/forums/forumdisplay.php?f=68)
-   -   pic: Who should have gotten the foul? part 1 (http://www.chiefdelphi.com/forums/showthread.php?t=115256)

savage 22-03-2013 11:24

Re: pic: Who should have gotten the foul? part 1
 
If a bot has at least one way of egress from a possible pin, like in this match that your complaint is about then there should be no pin called or blockading. As 3284 sole role in the match was to block the shooter. Now my .02 i think the GDC needs to change the max height rule for when you are on one side of the field or the other. They have done it in the past I just cant remember at this time.

And for the last time NO Instant REPLAY EVER!!!!!!!!!! Most events run late as it is, and this is why we have 5-6 REFS on the Field at one time, to cover all the zones. Yes they miss calls but so does the NFL and they have replay.

But Back to the match on hand, the Red Alliance should have seen this coming and changed their game plan. They got Tunnel Vision and missed the other two bots scoring undefended, which was a huge mistake and cost them the match.

Zakreon 22-03-2013 12:24

Re: pic: Who should have gotten the foul? part 1
 
You're pretty well spot on there Todd. Red received a technical foul for blocking our team from returning to the autonomous zone, and we received a regular foul for moving out of the zone before our net could lower. There were also 2 separate fouls on red for contacting the blue pyramid.

1288 also had a great shooter, but it was broken in this match, they couldn't shoot. 1706 was their only viable offensive bot, it actually does make sense that both 1288 and 1444 would be trying to push us out of the way to let 1706 score.

ToddF 22-03-2013 13:08

Re: pic: Who should have gotten the foul? part 1
 
I saw two touches of the pyramid, one at 1:30 and one at 1:35. I reviewed the rule for pyramid touches:

G27
ROBOTS may not contact or otherwise interfere with their opponents’ PYRAMID. Inconsequential contact will not be penalized.

For the first touch, the only robot touching the blue pyramid was the red robot, so the contact was inconsequential. For the second touch, a blue robot lined up on an opposite corner to shoot while the red robot was still touching. I ruled this as also inconsequential.

At 2:02, at first it looked like red might have touched while blue was hanging, but I could see a white disk on the ground between the red robot and the pyramid, so no touch.

Zakreon 22-03-2013 13:33

Re: pic: Who should have gotten the foul? part 1
 
Those may have been unwarranted, but I do believe that they received fouls for the contact.

Shane 2429 22-03-2013 14:57

Re: pic: Who should have gotten the foul? part 1
 
I agree that it was a bad call because you can clearly see that the defender could have dropped their net and in all reality the driver of the robot should have seen that in a 2v1 push match he was going to loose and in all reality those two robots were just trying to protect their shooter

I also seen the possible pinning call that could have been made though in all reality somebody messed up in the scouting for that match cause whoever was originally defending was way too underpowered to be trying to defend against that robot.

Also there is a point in match when you need to switch strategy cause there's was no reason why those other two robots on blue should have had free reign in their shooting ally .

Zakreon 22-03-2013 15:09

Re: pic: Who should have gotten the foul? part 1
 
Actually we aren't able to lower the net unless we can quickly jerk the bot around, its a problem with how the brackets connecting to the net are designed. We are making new brackets for our next regional to correct this problem.

ericbanker 23-03-2013 08:59

Re: pic: Who should have gotten the foul? part 1
 
Quote:

Originally Posted by Zakreon (Post 1251256)
1288 also had a great shooter, but it was broken in this match, they couldn't shoot. 1706 was their only viable offensive bot, it actually does make sense that both 1288 and 1444 would be trying to push us out of the way to let 1706 score.

1288's shooter was broken? :eek: So that's why they were forced to play defense. Does anyone know when and how that happened? 1288 had a really great robot, their shooter was a bit better than ours, and what I believe was a sideways turned holonomic/mecanum drive was really innovative.

Edit: I just rewatched the matches and they were shooting fine in the 1st finals match. They must have gotten damaged from the impacts by defenders in that match...but then they score a buzzer beater into the 3 point goal. So I'm still lost on what happened. In match 2, their autonomous fails to launch discs, and you can hear it clicking.

bulbajackel 23-03-2013 12:16

Re: pic: Who should have gotten the foul? part 1
 
Quote:

Originally Posted by ericbanker (Post 1251500)
1288's shooter was broken? :eek: So that's why they were forced to play defense. Does anyone know when and how that happened? 1288 had a really great robot, their shooter was a bit better than ours, and what I believe was a sideways turned holonomic/mecanum drive was really innovative.

Edit: I just rewatched the matches and they were shooting fine in the 1st finals match. They must have gotten damaged from the impacts by defenders in that match...but then they score a buzzer beater into the 3 point goal. So I'm still lost on what happened. In match 2, their autonomous fails to launch discs, and you can hear it clicking.

It happened somewhere where the robot just didn't respond to the field i believe. I don't know the specifics, but whatever happened there almost changed things. Didn't they start looking for a replacement?

Zakreon 23-03-2013 13:06

Re: pic: Who should have gotten the foul? part 1
 
A teammate told me that their cam that raises the shooter broke in some way, so the shooter could not properly move into position to fire


All times are GMT -5. The time now is 22:37.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi