![]() |
Re: Intentionally blocking traffic in Hybrid
For the people who are saying you should be allowed to block and that teams with good auto modes should "deal with it", could you please tell me why you should be able to? If you arent able to obstruct during teleoperated, why should you be able to in hybrid? I dont think you should be able to block in hybrid. In teleoperated mode, if someone is in your way, you can bump to pass. Robots arent going to respond to that in hybrid. So how can they allow teams to block. I'm not just saying this because our team has a great auto mode either. I havent gotten a chance to work on auto mode at all with the finished robot. If we have anything, I will need to do it on thursday at the comp. I really dont think teams should be able to block, however whatever the GDC decides I will be ok with.
Joey |
Re: Intentionally blocking traffic in Hybrid
For those of you so intent on quoting the Q&A as your reason for insisting that hybrid "blocking" (note that the term blocking is not defined anywhere in the rules) is illegal, PLEASE consider this Q&A, and LACK of direct answer by the GDC. The scenario put forth seems to be exactly what you are all complaining about - It seems that if the intent of the GDC was to dis-allow that specific strategic hybrid defense they would have made it clear in an answer to that question.
Note, in fact, that the only time ANY form of the root "block" (non-electrical, non-hotel) is used in the rules is in section 7.3.5.2, rule G43, which refers to "effectively blocking the width of the TRACK", and NOT just a single robot blocking a path. (THANKS team358.org !) |
Re: Intentionally blocking traffic in Hybrid
From the Q&A:
GDC GDC is offline Senior Member Join Date: Jan 2006 Posts: 1,411 Default Re: Hybrid Blocking Rule <G38> and Rule <G40> were modified to remove any concerns that teams may have about inadvertently impeding robots during the Hybrid Period. This was to avoid an unrealistic requirement that the robots be able to autonomously recognize and respond to "Bump To Pass" signals or identify and steer around stalled robots on the Track during the Hybrid Period. The purpose of these modifications is not to permit the intentional blocking of the Track during Hybrid Period. The accidental creation of obstructions on the Track during Hybrid Period may be unavoidable and will not be penalized. However, intentional strategies designed to block traffic during the Hybrid Period will not be permitted. This may be considered a Yellow Card offense. We shall see how FIRST responds this week, especially in light of the fact we have teams admitting to intentionally impeding in HYBRID mode. On the other hand, this is a great strategy to use against great hybrid mode robots. We shall see. |
Re: Intentionally blocking traffic in Hybrid
This is going to be hard to rule. Teams that move, but do not move out of their first quadrant should be excused from the high speed ramming rule, meaning if they are in there, they better expect consequences for their choice to run that auto mode. Having to make the more capable teams give the right of way to the teams that impede traffic goes against the regular match play. These rules seem to become more complicated for reffing as these updates come out.
I do agree it is a great idea for them to do as a defensive strategy, but penalizing the other person for falling into their trap isn't right. It's like a person parking their car in the middle of the freeway...try explaining to the auto insurance why you caused the 5 car pile up and how it's their fault for you voluntarily parking there. |
Re: Intentionally blocking traffic in Hybrid
Quote:
|
Re: Intentionally blocking traffic in Hybrid
In my eyes the high speed ramming is still a very plausible call in autonomous/hybrid, even if the robot intentionally moves into the way to block said rammer (intentional/unintentional potential damage to a robot is a very serious problem and should merit a warning on first offense). Our team received a warning the first time, and a yellow card the second, for entangling other teams in our accumulator (very unintentional). Also, the idea of intentionally moving into possible lanes of traffic is a very legitimate strategy (as long as there is still a lane wide enough for a robot to fit through as far as the track is concerned). 1024 has a very very well thought out completely autonomous mode that will slow down to "gracefully" push obstacles out of their way (or attempt to avoid them in general). 1114 has the advantage (disadvantage?) of using the robocoach to tell their bot when to turn (brings in human error and field of vision). Finally, I feel that all of the matches were spectacularly played by every team on the field and I can't think of anyone better to lose to.
Thank you for your time, Alec Hill |
Re: Intentionally blocking traffic in Hybrid
Quote:
|
Re: Intentionally blocking traffic in Hybrid
Quote:
Please, for the sake of a decent debate, no longer use the word impeding, it is not what this debate is about anymore. (That is not a personal attack on you David, just a request to everyone) |
Re: Intentionally blocking traffic in Hybrid
Quote:
I really don't follow this logic, the Q&A section is listed within the 2008 Competition Manual and Related Documents, It has a printable export file that coincides with the manual that could be represented and read at competitions or before hand. Tho the quotes we use do not have an R# or G# Quote:
Quote:
Quote:
That said, I still don't understand how people can shrug this off as at the very least an official interpretation, regardless if it has any official weight during the matches. The question is direct, and the answer is even more direct, I guess you can argue about whether teams meant to block ( keep in mind it doesn't mention impeding ), but most have openly stated it was their strategy. Honestly, as I watched the matches I thought the same way as most of you, but after reading this Q&A I just am having trouble seeing the otherside of the argument at all, and trust me, I've thought about it possibly more than any of you because of the responses that I got on my last post. But baring an official interpretation, I can't possibly see how any of the teams I participate would use this strategy until its officially cleared up. Call me a Moral Crusader, but I don't like to tread too deep in the Grey Areas, because the black just creeps up on you to quickly. I really could care less which way FIRST decides, but I'm pretty sure my head will explode in this quagmire of ambiguity if they don't decide soon. |
Re: Intentionally blocking traffic in Hybrid
Dan,
We agree that it is clear, but just not what is clear. The rules and updates are official. The rules and updates provide a clear direction that one robot can't possibly impede. The Q & A are irrelevant on a rule that is clear in the manual and update. When the GDC uses the word block, they seem to throw in "the entire track" or "the flow of traffic." Look at St. Louis finals match 1 where 45 blocked by driving 7 feet and stopping. They clearly did not impede as both robots passed by them just fine. One robot can't impede unless it is weaving back and forth, which is also specifically called out in the rules. |
Re: Intentionally blocking traffic in Hybrid
Quote:
Dictionary.com ( because its easy to cut and paste ) makes three references that I would assume to be relevant in 4, 6 and v. intr 1. Quote:
Really I guess I can only see two ways to address this problem, Update the purpose of Q&A or update a bulletproof clarification with no vague answers on the Q&A. For the Q&A's sake partial applied weight doesn't make sense to me, either make it equal to the updates OR get rid of it as a public forum. I realize at a competition this is kind of what a referee group does by specifically clarifying intent in driver meetings and by established a precedence in their calls. This all comes by what was handed down to them by FIRST. But to have one FIRST document say one thing and one say another is ludicrous, its wishy washy, it creates confusion, and those who can't adapt to the clarification at competition suffer greatly, when they did all they could to prepare before they got there. |
Re: Intentionally blocking traffic in Hybrid
I'm not a physics student, but maybe someone can help me out with a bit of math... Say we've got a 150lb robot, moving at 20fps (a high speed hybrid/auton mode). It impacts another 150lb robot, square on. That has to be a HUGE amount of force. What I think needs to be implemented is a new mode for robots: If you detect a hit on someone who impeded your auton, back up, and ram repeatedly until the time is over. All you need to do is take one penalty for intentional ramming, and NO ONE will get in your way for the rest of the season. All it takes is one frame being reduced to scrap metal to send a clear message, right?
(for those that don't get it, that was sarcasm. I personally think the issue is near impossible to definitively rule on, and won't really be solved. I think teams need to shape up, and not mess with the high power team's hybrid/auton.) |
Re: Intentionally blocking traffic in Hybrid
Quote:
|
Re: Intentionally blocking traffic in Hybrid
Quote:
Here's my contention - people can suggest you read every last bit of the Q/A and say that such rulings are official, but I live in the real world, and in the real world, teams and individuals barely have enough time to finish their robot, let alone spend hours reading hundreds of Q/A responses TO QUESTIONS THEY DIDN'T ASK and comparing them against the existing rulebook. Judging from this past week's events, I'd say the VOLUNTEER REFEREES also have difficulty finding time to perform such analyses. If someone feels a Q/A ruling is important enough that everyone and their brother should know about it, PUT IT IN A TEAM UPDATE, SEND IT OUT IN AN EMAIL BLAST - do what Woodie Flowers endorses and COMMUNICATE. As far as I am concerned, NO Q/A response involving an important rule clarification is official until FIRST ensures it is properly communicated to everyone via appropriate and logical channels. Expecting everyone, including referees, to unearth the answers for themselves only unleashes the three-headed dog of inconsistency, confusion, and anger we are witnessing here in this thread. Now I know there are teams out there that read this and go "Wah. We have Q/A Rules Compliance Officer Steve who spends half his life refreshing the Q/A every 2 minutes so we are always in compliance with every last response." You may feel pretty darn proud of this fact, and indeed, I commend thee for being so meticulous, but please don't stand up on your pedestals and look down with scorn upon other teams who may not be as efficient as yourselves or have the people or time to devote to such endeavors. Thoroughly reading the manual and team updates is the responsbility of all teams. But sifting through the mass quantities of debris in the Q/A trying to glean the few true nuggets of gold among the miles of redundant and unimportant rulings is just asking too much. Please, cut the teams some slack and COMMUNICATE with them. I think $6,000+ buys them at least that. A simple Team Update blurb and/or Email Blast would have alleviated all this controversy. Once any official ruling on this matter is communicated to all, my team will abide by what is decided. Until then, since it was permitted in the *real* *world* at numerous Week 1 regionals, we will continue to use hybrid blocking at our discretion. |
Re: Intentionally blocking traffic in Hybrid
With team update 14 released, and no mention to this rule in it, it's probably going to stand. Odds are that impeding will be permitted in future competitions =O
|
| All times are GMT -5. The time now is 15:49. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi