Team Update #18

[Lil' Lavery]

To expand upon the difference in a safety perspective:
this
vs.
this

You make the call on which is safer.

[Vikesrock]

Originally Posted by Lil' Lavery

To expand upon the difference in a safety perspective:
this
vs.
this

You make the call on which is safer.

I disagree with this example.

How about
this
Or
this
Or
this
Or the many other times this has happened with no defense.

VS.

this

For the record I think as a last ditch effort this is not a bad idea, but it should be just that, a last ditch effort.

I also happen to disagree with FIRST changing the rules this late into the season.

I don't think that this would have become a widespread strategy with, or without the update.

[David Brinza]

Do you think that stacking one robot (or more) on top of another and sitting there for an entire match is consistent with the spirit of the game or, for that matter, FIRST?

I don't. Teams that wish to adopt this strategy are putting winning ahead of competing (yes, there is a difference - winning at all cost is not GP).

I'm not slamming Wildstang here; their alliance partners were basically non-functional and this strategy gave their alliance the possibility of winning that match. I doubt that any competitive teams would consider doing this with functioning partners. It's just too much fun to drive your robot and earn a victory!

Maybe Update #18 falls in the category of "legislating morality", but I don't think we want to see a lot of matches with an alliance just parked in their home zone for 2+ minutes. The lack of autonomous action is dull enough for me...let's PLAY the game!!!

[Daniel_LaFleur]

Originally Posted by David Brinza

Do you think that stacking one robot (or more) on top of another and sitting there for an entire match is consistent with the spirit of the game or, for that matter, FIRST?

Actually I do think it is consistant with FIRST.

Teams that are overcoming adversity is exactly what FIRST is about. Both robots were (from my understanding) broken and would not have been able to do anything. So what do they do, they stack and help their alliance to a win.

Thats teamwork. Thats overcoming adversity. Thats innovative thinking. Thats FIRST.

[Kevin Sevcik]

Originally Posted by David Brinza

Do you think that stacking one robot (or more) on top of another and sitting there for an entire match is consistent with the spirit of the game or, for that matter, FIRST?

I think that's completely beside the point people here are trying to make. Many people arguing against this call see perfectly clearly the logic and reasoning behind it and don't have all that big a problem with that logic. The issue we have is with the complete and utter arbitrariness that FIRST and the GDC have been exhibiting this year. This very issue was asked in the Q&A just one week into the build season. The answer then was that it was ok, so presumably the GDC had no problems with it then. Then, after 3 weeks of competition have gone by and they've seen it happen just once, they suddenly decide they don't like it anymore and arbitrarily rescind their approval. They don't even attempt to smooth over their change of mind with any of their own reasoning along the lines of all these arguments we're having about safety and the spirit of the game. It's frankly getting a rather lot like something out of "Through the Looking Glass" trying to guess which way the wind is blowing each week. The Q&A question is particularly weird. The original question and answer came just before Update #3. And the GDC's followup suggests you consult Update #18 to discern their latest state of mind.

We don't mind picky rules, weird rules, somewhat unfair seeming rules, so long as the rules actually stand still for most of the season. Aiming at a target that's still moving long after build season is over asks far too much of teams.

[David Brinza]

Originally Posted by David Brinza:

Do you think that stacking one robot (or more) on top of another and sitting there for an entire match is consistent with the spirit of the game or, for that matter, FIRST?

Originally Posted by Kevin Sevcik

I think that's completely beside the point people here are trying to make. Many people arguing against this call see perfectly clearly the logic and reasoning behind it and don't have all that big a problem with that logic. The issue we have is with the complete and utter arbitrariness that FIRST and the GDC have been exhibiting this year. This very issue was asked in the Q&A just one week into the build season. The answer then was that it was ok, so presumably the GDC had no problems with it then. Then, after 3 weeks of competition have gone by and they've seen it happen just once, they suddenly decide they don't like it anymore and arbitrarily rescind their approval. They don't even attempt to smooth over their change of mind with any of their own reasoning along the lines of all these arguments we're having about safety and the spirit of the game. It's frankly getting a rather lot like something out of "Through the Looking Glass" trying to guess which way the wind is blowing each week. The Q&A question is particularly weird. The original question and answer came just before Update #3. And the GDC's followup suggests you consult Update #18 to discern their latest state of mind.

We don't mind picky rules, weird rules, somewhat unfair seeming rules, so long as the rules actually stand still for most of the season. Aiming at a target that's still moving long after build season is over asks far too much of teams.

So, your issue is with FIRST GDC flip-flopping on rules interpretation, and perhaps that's a valid concern. However, I think that as the season plays out, events will occur that the GDC didn't anticipate. I don't think the FIRST community has the expectation that the GDC has all identified ALL of the potential game scenarios by kickoff or even before the first week of competition. I suspect that the "stacked robots at start" scenario, when witnessed in competition, was deemed by the GDC to not be a good thing for the competitions. I would not like to see this as a widespread practice in matches. If I saw robots stacked at the start of a match, the temptation to "destack" them would be great - if a 10-pt penalty were incurred, it's a 20-pt net win to knock down the stack. To avoid alliances from trying to score an "easy" 30 points and to avoid the risk to robots from executing the obvious defensive action against this ploy, I suspect the GDC felt it necessary to close this "loophole".

I'm not attacking you here (I'm directing this question to the broader CD community), but would you put your functional robot on top of a partner's robot and sit there the entire match in order to win? Would you intentionally make your robot appear non-functional (remove breakers, break your chain, etc.) in order to stack your robot if the rule was written such that only non-operational robots would be permitted to stack? I think these sorts of questions are pondered by the GDC in making/changing rules for the game. Please keep in mind that we see a new FIRST game every year and even in sports that have been around for a long time, the rules change season-to-season (and maybe even mid-season).

BTW, If you answer "yes" to either of the above, I guess that the GDC has really impacted your strategy. I, for one, feel that the rules should NOT allow this strategy. Even if the rules are written later rather than sooner.

[GaryVoshol]

Originally Posted by Lil' Lavery

To expand upon the difference in a safety perspective:
this
vs.
this

You make the call on which is safer.

Versus this: http://www.chiefdelphi.com/forums/sh...ad.php?t=55601

No where did the GDC say it was a safety issue. They simply closed a loophole that had been left open from the beginning of Build, without giving any reason. They have the right to change the rule. The question is, why wait until now, when they were questioned about it weeks ago?

[lenergyrlah]

Originally Posted by GaryV1188

Versus this: http://www.chiefdelphi.com/forums/sh...ad.php?t=55601

But since most robots aren't designed to be that short while in starting configuration the liftees would be a lot higher. At least those fallen robots were still in 1 piece -- i'd hate to see that happen to a robot perched four feet off the ground.