![]() |
Re: Team Update #13
There are a lot of "may" and conditional words...
The judges never looked fondly on our defensive robot last year and called us to the carpet on a lot of these wholly-subjective violations. Robots like Dragonfly can run into this problem. Be nice to your judges. |
Re: Team Update #13
woah wait.
<G23> Contact (via ROBOT or GAME PIECE) with the opposing ALLIANCE’S TOWERS is prohibited. Violation: PENALTY plus RED CARD Am I reading it right to say that is anytime during the match? |
Re: Team Update #13
Quote:
|
Re: Team Update #13
Quote:
That said, adding a penalty for a yellow card action is not a bad idea necessarily. There have been situations where yellow card actions were the best move strategically... |
Re: Team Update #13
I think the update is a response to feedback to the ref rules test.
I think the GDC assumed that when a rule is violated a penalty would be given unless stated otherwise. These changes make sure that this is the case not just a supposition. When I took the test I flunked the first time because I didn't make that assumption and missed the red/yellow card AND penalty part on some questions. I passed when I added penalty to my answers. |
Re: Team Update #13
<G21> HOSTBOTS may DEPLOY MINIBOTS only onto their ALLIANCE’S TOWERS and entirely below the DEPLOYMENT LINE. Violation: PENALTY plus RED CARD.
So if you deploy a bit to high, you get a RED CARD? I would think that it would at worst be a YELLOW CARD with the TOWER disabled. |
Re: Team Update #13
While none of the updates in particular bug me, I am also bothered by the fact that there are so many of them, and that game is getting lawyered to death already and we haven't even started playing.
My favorite games are all the ones with the simplest rules, and the relative freedom. Teams come up with interesting things, and to stifle that with a quagmire of hard to consistently enforce rules is... irksome. FIRST/GDC has done better in the past, we know they're capable of this, I just don't understand why they haven't strived to continue that. |
Re: Team Update #13
Quote:
Please remember that GP means different things to everyone and nobody should use it as a means to condemn or justify actions. When it comes to GP, there are no definite answers as to yes or no. |
Re: Team Update #13
Quote:
|
Re: Team Update #13
Quote:
Shall we keep this conversation about the updated and not turn it into another "This is what GP means to me" thread? There are several running around here somewhere... |
Re: Team Update #13
Just as important is today's Bill's Blog entry: http://frcdirector.blogspot.com/
Quote:
|
Re: Team Update #13
Quote:
|
Re: Team Update #13
Quote:
Actually this is always one of the biggest issues with tubes or anything inflated like this. Pressure plays a huge role and it fluctuates based on the temperature of the event. I wonder if tubes will be periodically rechecked through the day. |
Re: Team Update #13
Quote:
|
Re: Team Update #13
Quote:
If your cylinder is pushing up you arm, what if you had a mechanical lock the arm so that when it reached the desired height, you would lock it in position? If you had a sprocket-like piece on the arm at the pivot, and another toothed piece that locked into the first but didn't rotate, it would effectively lock your arm in position. I don't know the technical term for the part I am describing, but I see them used on some microphone stands and stands for percussion equipment in band. You may want something more industrial than what is shown here, but here's a picture of what I am struggling to depict. I thought maybe you could either use a motor(to turn a screw as intended purpose of this specific product) or a non-rotating piston to actuate the lock. http://www.fullcompass.com/common/fi...A9500_List.pdf Has anyone ever tried what I am describing? |
| All times are GMT -5. The time now is 00:54. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi