![]() |
Team Update 1-15-2013
http://frc-manual.usfirst.org/Updates/0
Edit: I read it right, but I wrote it wrong. I meant that if touching the pyramid then the 54 inches relates to the robot instead of the field. |
Re: Team Update 1-15-2013
Quote:
EDIT: Fig 3-5c explains it, I see it now. |
Re: Team Update 1-15-2013
Try again. They added G23-1, saying precisely the opposite.
To be precise, the 54" cylinder reorients with the robot WHEN touching the pyramid. |
Re: Team Update 1-15-2013
And we just re-engineered our stuff to fit within relative to the floor (meaning some of it is possibly illegal now) :/
|
Re: Team Update 1-15-2013
I noticed that the word vertical is crossed out. does this means that we can be in a 54" oblique cylinder when not touching the pyramid?
|
Re: Team Update 1-15-2013
I'm really holding back, but did the GDC just change the task?
|
Re: Team Update 1-15-2013
The way I interpret it, vertical is crossed out because while in contact with the pyramid the cylinder isn't vertical
|
Re: Team Update 1-15-2013
Man,
I need some time to re-re-re-read the rules. :yikes: |
Re: Team Update 1-15-2013
Stupendous. Magnificent. I cannot express my gratitude and appreciation for the GDC changing this rule a week and a half after kickoff after we reluctantly scrapped our plans for a lifting and dumping robot.
Presumably all the 54" cylinder questions they were getting made them question whether anyone was actually going to attempt the end game, so they decided to relax the rules to make it easier. Well at least they didn't reconsider after seeing several technically illegal robots at the week 1 regionals. |
Re: Team Update 1-15-2013
So the 54 inches reorients with the robot, is this in relation to the bumpers? Or am I not seeing something here?
- Andrew |
Re: Team Update 1-15-2013
WOW. They answered this question completely differently in the Q&A and then change it a week later? With such a restrictive design requirement, how can the GDC possibly not have the details down?
|
Re: Team Update 1-15-2013
So our process was to design it, change it to make it work, and now find out we didn't have to change it? Yay?
|
Re: Team Update 1-15-2013
1 Attachment(s)
Here is the picture from the update... since this robot has no bumpers and no frame perimeter it is hard to tell but it does say robot relative...
|
Re: Team Update 1-15-2013
Robot relative typically means relative to your starting/inspection configuration. Whatever orientation is vertical when you start the robot is the vertical direction for your robot throughout the match.
The reason this makes climbing easier is that you can tip your robot over and reach up to 84" vertical relative to your robot, which is a good bit farther than the 54" cylinder restricted you to. |
Re: Team Update 1-15-2013
that gives a diagonal(which could become the true vertical when touching the pyramid)of nearly 100 in.(99.859). That makes it technically viable to sacrifice the legality of your own robot's climb to attach a winch to level 3 and bring 2 robots up with you, scoring 60 points.
|
Re: Team Update 1-15-2013
Makes the stair chair strategy viable.
|
Re: Team Update 1-15-2013
what is this 'stair chair' you speak of?
|
Re: Team Update 1-15-2013
|
Re: Team Update 1-15-2013
Our climbing solution is now illegal.
We had clearly defined parameters at the beginning of the build season. Why on Earth would they change now? |
Re: Team Update 1-15-2013
I hate everything 3 times.... Just kidding, this makes things easier but also more difficult. it means that our previous strategy is now illegal but simpler strategies are now legal and can be made lighter, cheaper and safer.
|
Re: Team Update 1-15-2013
Quote:
FIRST should ask teams to designate a co-ordinate system relative to some component (e.g. with a sticker).1 All robot-relative restrictions should be measured with respect to that. Alternatively, starting/inspection configuration can be defined, and robot-relativity defined in relation to that. Failing that, robot-relativity is ambiguous. 1 Don't use the frame perimeter. It's a trap. The definition allows for skew polygons and planar polygons not parallel to the floor. |
Re: Team Update 1-15-2013
I can't stand when FIRST does this. Why make it part of the rules if you're going to change said rules after a week? Crucial design elements are being set.
The one benefit I see from this is that it mirrors real world projects more closely as a learning tool, but man is it frustrating! Back to the drawing board! |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
I do not like this at all. I know it was difficult but we designed, prototyped, had a lot of the CAD work done, and had parts list ready to order in the morning. All for not, because our whole design is shot thanks to a mid-season rule change. Sorry move my the GDC in my opinion. Back to the drawing board I guess... ARRRRRG
|
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
We find out that the bumpers count in the 54" cylinder.
Design Change. Now we find this out. And another design change is needed. At least this one will hopefully not be too drastic of a change. |
Re: Team Update 1-15-2013
Should I be worried that our design didn't change?
|
Re: Team Update 1-15-2013
Why changes the rules at this point? Did the GDC just realize that climbing for 30 was hard? Luckily, this didn't change much for us, but it totally redefines the design challenge.
|
Re: Team Update 1-15-2013
Aaaarrrrrrg! Blows our climbing design - and our chassis design - out of the water...
|
Re: Team Update 1-15-2013
Quote:
Even though this actually makes it easier for us, I cant believe FIRST is making such a huge change that actually makes some designs ILLEGAL after a week and a half. Unbelievable. |
Re: Team Update 1-15-2013
Quote:
In terms of using bumper edges as the reference, there are similar issues. The bottom edge of a legal bumper can (in theory) be between 2.0 in and 5.5 in from the ground, meaning significant angles are possible. Edit: I re-read your post, and may have misunderstood it the first time. Are you suggesting that we construct the robot-relative co-ordinate system based on something like the the starting bumper orientation and the ground normal? (Hopefully the floor protector doesn't figure into this.) Then, because the bumpers can't articulate, we can use them to observe the orientation of the robot-relative co-ordinates during the climb? That has interesting implications (like when bumpers fall off), but could be feasible. However, I don't think the rules support this interpretation to the exclusion of others. |
Re: Team Update 1-15-2013
![]() So is this not legal now? Excuse the crude drawing |
Re: Team Update 1-15-2013
It has been a long day with robots of plastic and aluminum at both ends. We're slow and were doing full-scale modeling to determine our compliance with 54" rule in its prior form. Now I read of the rules change and that several teams are feeling that their initial designs are now illegal. This is where the tired part comes in. I'm having trouble imagining how something legal for the vertical cylinder is now illegal for a tilted one. I'm sure those are right, just in a FRC fog at the moment I guess.
|
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Our design, our beautiful design, is in serious, serious question right now.
blog. blarg. ugh. This.Inhales.Audibly. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
edit: just imagine slicing a plane through a vertical 54 inch cylinder at a 60 degree angle. edit2: this is only one example |
Re: Team Update 1-15-2013
Quote:
Didn't read this: Quote:
|
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
I'm happy to say that my team's level 3 climber design is still legal :D
|
Re: Team Update 1-15-2013
Quote:
Note: Haven't figured out the rule that says bumpers must be "vertical." R24-E comes close, but doesn't quite do it. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
I'm not trying to look flippant, but in the real world engineering specifications change all the time.
FRC: more like the real world than we could ever want. |
Re: Team Update 1-15-2013
Quote:
This is a disappointing ruling from the GDC. Major changes like this shouldn't be necessary to the size restrictions, which are some of the most crucial rules teams have to design around. Coming in week 2 as teams are finishing prototypes and some have begun ordering parts is the real kicker. |
Re: Team Update 1-15-2013
Looks like we found a relatively simple solution to fix our climbing for this update. However, this could have easily been a complete disaster for us since we are integrating all of our functions into one mechanism this year. I feel for all the other teams who will not have as easy of a time making their designs legal if they will even be able to use it at all.
|
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
I'm surprised by this change since they already answered it in the opposite way previously. Better now than later, I guess, but this is a question that could have reasonably been anticipated and clarified before the game was released.
This didn't blow our climbing concept out of the water, but I'll be watching closely for a bumper clarification that has the potential to cause us trouble. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
I agree with the others who call this a bad move and bad form on the part of the GDC especially when this was discussed completely in a mentor call and it directly contradicts an earlier answer in the formal Q&A (which is also hosted by the GDC). :mad: |
Re: Team Update 1-15-2013
Has FIRST ever made such a big change like this before?
|
Re: Team Update 1-15-2013
Quote:
As others have pointed out this is probably the optimal (fewest illegal robots) solution, even if causes rework. And I know that rework is annoying. |
Re: Team Update 1-15-2013
Quote:
I think calling the rework annoying is an understatement... Full design and CAD just having some of the details added, and now we have to change it completely. I'm still reeling that this drastic a change has been made this long after kickoff. Do you suppose the GDC will reconsider given the backlash and how clear the Q and A seemed to make the rules before? :mad: |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
They've changed size dimensions before as well, I don't know if it's always been so critical to a task like this though. |
Re: Team Update 1-15-2013
Quote:
I agree with your 5% comment; however, manufacturing and resources aside, time is still the most valuable asset in an FRC season. There will definitely be other solutions, I just have a hard time believing that this rule will result in more successful 30 point climbs (which is my interpretation of the purpose of the change). |
Re: Team Update 1-15-2013
The basic reason I can see them doing this is for enforability. It's already difficult to determine if the robot will fit within the 54" cylinder when on flat ground. Robots breaking the cylinder when transitioning between levels while climbing (especially unintentional) is basically impossible for the refrees to be certain of. In close matches no one wants the deciding call to be made by a ref who from 15 feet away may have seen a robot momentarily break an invisible cylinder...
|
Re: Team Update 1-15-2013
Is it possible this rule change was more in response to concerns that robots that fall over would be in continuous violation, rather than concerns about complex climbing mechanisms? I know that was discussed as a concern at the beginning of the season.
Still stinks though, especially for cool ideas like some that have been spoiled now. Very sorry indeed, folks.:( |
Re: Team Update 1-15-2013
Quote:
2002: Rules and rulings associated devices that look like motorized tape measures were reinterpreted at the events. (Affected parts usage and entanglement.) 2003: Rules for reacting against field elements were changed in March, after the build season. (Ruined 68's strategy.) 2011: A rule against strategically blockading the field was inserted in week 5. 2012: Changed the definition of bridges in week 6. (Ruined 3928's strategy.) Edit: For clarity, week numbers identified above were during the build season. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
when this update came out, I realize that our ingenious and rather fast climbing design was previous illegal, but it is now 100% ok. sighs of relief all around our shop table, but i can see it's not so great for other teams. sorry to all those team out there, i know how it feels since our balancing arms from last year were ruled out late in the season because they sometimes touched the polycarb sheet under the bridge.
|
Re: Team Update 1-15-2013
Quote:
Obviously an incentive to be in two places at once. Teams Q&A'd for ruling on what constituted an entanglement hazard, etc. and it seemed clear that anything long and flimsy was an entanglement hazard and illegal. So some teams went to a lot of trouble making mini-robots or rigid extension devices to reach across the field to score those bonus points. Week 1 regionals and some few teams show up with motorized tape measures that they shoot across the field. Which seemed obviously illegal. Except the GDC ruled that they were, in fact, legal because they And thus all the teams that put in a lot of work and engineering to come up with a non-entangling solution were really miffed at a huge rule change after the end of build season. |
Re: Team Update 1-15-2013
Quote:
Wait why? This was a very interesting story, pity you stopped right when it was getting interesting :P |
Re: Team Update 1-15-2013
I think the despair expressed in this thread might be premature.
The updated rule reads (in part): Quote:
I foresee a referee noting a possible infraction, then checking after the match by having the team reposition their robot as it was when he had doubts to its legality (even if it has to stand on a bumper!). Once the robot is in the configuration, a hoop is passed over the robot. If the hoop can be extended vertically without contacting the robot, the robot was legal. |
Re: Team Update 1-15-2013
When you look at the rule change, it seems that the intent of the rule could be to prevent a team from latching on to the pyramid and then extending towards the side of the playing field, in order to attempt to blockade the field (circumventing the other rule?).
|
Re: Team Update 1-15-2013
Here is my interpretation of the new rule and how is kills our design that was so close to sending parts our to be machined. I hope the GDC changes its mind. Since in all likelihood this bot will not come to life in its current form I thought I would share.
![]() Old Rules - Legal ![]() New Rules - Illegal |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Tristan already brought up some good points as how the definition of coordinate systems affects what is "relative to the robot".
IMHO, simplest way to word the volume restriction rule would be to state that: Quote:
Basically, at any given point in time, your robot must be able to be dropped into a giant virtual bucket that's Ø54" x 60"/84". As long as it can fit inside this bucket in some orientation, it's a legal configuration. Much simpler for people to comprehend, and it does not negatively affect teams who based their designs on the pre 2013-01-15 update rulings. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
It allows officials to use the least-restrictive interpretation of what it means to be robot-oriented, and lets much of the existing design work stand. On the other hand, it may go against the GDC's intent, but that's the price FIRST needs to pay for not adequately capturing the intent in the first two versions. More practically, it's hard to judge the size of a 3-D cylinder superimposed over a moving robot climbing an obstacle. But since it was hard enough to judge the size of that cylinder when it was oriented with respect to an obvious reference, presumably FIRST has thought about this sort of thing and can devise some way of enforcing it when the orientation is completely arbitrary. (Hopefully "ignore it" doesn't figure into the final cut.) |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
Do you have a cylinder model of your robot when it is still on the floor, and has just grabbed on to the 1st rung? Most corner climbers with a squarish to longish drivetrain will have a hard time reaching the 1st rung without breaking the cylinder. Not impossible, but it's very tight. |
Re: Team Update 1-15-2013
Hopefully this is just a wording inconsistency and a clarification will be coming where the GDC states they did not just 'turn the rule on it's side'.
/pun intended. |
Re: Team Update 1-15-2013
Quote:
Thankfully our design -which we spent excessive time on to get it within the previous rules - will still work with the new definition. Probably would have saved us half the week if we had this definition to start wth. Grrrrrrrrrrr. |
Re: Team Update 1-15-2013
Quote:
"...I get the feeling the kids won't be very phased tomorrow" I'm not so sure I agree with you. For my small town team who just started getting noticed by the corporations (think funding) we have been courting for 6 years we were looking forward to possibly the best robot we have ever built/designed. We have (had) a corner climbing bot that we belived would be among the best climbers out there...now? Who knows what we will do until the team meets this evening. With limited engineering resources and funding this has the potential to hurt the morale of more than you may think. Frankly I know it has damaged mine. :( |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Don't forget about frame cutouts. It's possible to park the very center of your robot right on the bottom of the bottom post and grab the first rung without extending outside your frame perimeter at all.
|
Re: Team Update 1-15-2013
Our climber design is now illegal per the general interpretation of the updated rules. I had placed orders to McMaster, AndyMark, VEX, and BaneBots literally hours before the update. Now we have spent a good chunk of money and most of our PDV's on a design that is illegal. We've also wasted 10 days working on CAD and prototypes. :mad:
I have lived through all of aforementioned 'major' rules changes. Those changes, while frustrating for some, were designed to capture what was clearly the spirit of the inital rules and/or to prevent game-breaking designs that would ruin the event for other teams. The big difference this time is that this rules change is arbitrary. It serves no more purpose than to make some designs illegal and others legal based on the arbitrary orientation of the robot. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
Q184 I agree with what a few others have said: I hope the GDC clarifies that the old designs are still legal. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
I really don't see a reason that both virtical and robot oriented cylinders could be legal. The only thing this could possibly result in is a greater varience in design and more robots climbing for 30-- which are both good things.
Regards, Bryan |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
At least, that's the leading theory I've heard. Pretty lame when they figured that out a week in, after teams spent time, money and effort working around a thoroughly clarified rule. I sincerely hope FIRST gets it's head right here and realizes how frustrating it is for teams to be dealing with fundamental rules changes well into the build season. |
Re: Team Update 1-15-2013
Quote:
The proposed '54in cylinder in any orientation' rule is equally as enforcible as the 'robot-oriented 54in cylinder' but allows for a much wider variety of designs. |
Re: Team Update 1-15-2013
Quote:
Making it so both configurations are legal would negate the purpose of the rule change to begin with, or so it would seem. |
Re: Team Update 1-15-2013
Quote:
It's certainly possible, but very difficult, under the old rule to examine a robot and tell the refs "if the plane of the robots bumpers tilts more than 15 degrees while climbing and this appendage is fully extended, then it's illegal." Telling them that, however, and judging that on the field is a whole different story. Visually telling how long an appendage is extended is difficult, telling a precise angle is even more difficult. Combine the two in a moving environment, and it's an impossible task for the refs. The result? You would have two camps of teams. Those that paid very close attention to this rule and how it affects their robot while in different orientations while climbing, and those who didn't. You'd see both groups of teams climbing the pyramids, and no penalties called other than obvious, egregious violations of the rule. And one group, the group that's really upset right now, would be really upset that they spent so much time and effort complying with the rule, when a "simpler" design they decided was illegal is actually allowed. It's a catch-22 - either way the GDC went with this would make teams upset. Personally, I think the decision to update the rule to make it more enforceable is the right way to go. I might moan and complain if it forced my team to change our design, but it would still be the right way to go. What's the point of a rule if its impossible to be enforced on the field? |
Why didn't thy know that a week and a half ago?
|
Re: Team Update 1-15-2013
Quote:
I'd be happy to demonstrate that the robot design is legal per the original rule. Hauling it onto a pyramid and measuring would be difficult at best, but this is an engineering contest. We can do a simple report that examines the robot design in climbing orientation(s), bring that to inspection and use it to demonstrate to the inspectors satisfaction that we're legal. That kind of documentation is common enough in other competitions and business. A better solution is simply to write rules from the start that can be checked easily for compliance during inspection. Failing that, I would rather have unenforceable rules that are at least consistent, then the current moving goal post. After all, it might be moved only to ensure compliance that was already going to be there in 99% of cases anyways. |
Re: Team Update 1-15-2013
Given that the rules for the game have changed may be, just may be the GDC will extend the bag date by 10 days.
We could only hope for a dream to come true.. |
Re: Team Update 1-15-2013
I am very upset with this recent rule change. A rule change like this shakes the confidence teams have in FIRST. I though about this all last night. My team has spent a tremendous amount of time to make a climbing mechanism that fit the previous rules to find out that all this time was for nothing. I can see teams being more timid in the future because of this kind of action. Its not professional and looks like they had not put much thought into it. This climbing task is one of the most complicated ones that FIRST has asked us to do and playing with the rules concerning this is very frustrating. I understand that sometimes mistakes happen, but sometimes adjustments need to be made for those mistakes on both sides. Flexibility in the rules would seem to be the best solution rather than the hard steadfast "this is our rule" approach. I, however, am not paid the "big bucks" so my opinion may be wrong but it doesn't feel right to me. If I made a mistake and people suffered because of it and I wanted to keep the integrity of the game I would compromise for the good of the order. As Spock said "The needs of the many outweigh the needs of the few or the one". Spock may not be real but his quote sounds good to me. My team now is redesigning possible new solutions, and will be buying or making new parts because that's life, such that it is........
|
Re: Team Update 1-15-2013
1. This change is in direct contrast not only to the rules but several Q&A responses. Why the contradiction?
2. I don't buy the "enforceable" argument - this program is built on implied compliance. Example: bag n tag. 3. I really really hope TU4 says robots contacting pyramid can be either/or. |
Re: Team Update 1-15-2013
Quote:
|
Quote:
|
Re: Team Update 1-15-2013
This rule change completely invalidates our climbing concept. Countless hours of design, money spent on parts, fabrication started on a drivetrain, all for nothing. The rug has just been pulled out from under our feet. Simply demoralizing.
It's great to hear that the change helps some teams, but seriously... teams that have been following the rules and the spirit of the game are now being punished? It goes beyond reason. The only reasonable and fair way to change this rule is make it more inclusive (cylinder in any orientation, or vertical/robot oriented team's choice). I hope GDC reconsiders this change and/or clarifies the definition of relative to the ROBOT to be more inclusive. Quote:
|
Re: Team Update 1-15-2013
Quote:
Same here - our mechanism must be re-positioned and our frame changed. This was a big oversight! Arghhhh... |
Re: Team Update 1-15-2013
This rule change may be because it was difficult to enforce the previous one, but it certainly wasn't impossible. We are engineers, and if you are building your robot fit inside a vertical cylinder you probably can find a way to prove that it resides in it. I know they aren't set up for it but maybe there are autonomous ways to call violations of this rule. Four cameras mounted far above the pyramids with a little logic to determine if there is a 54" violation? Maybe that's just a dumb idea I thought of while writing this response but I do think it could be enforced. I know someone could think of a way. Just because it would be difficult to do so is something is a reason they should have thought about before releasing the rules, or the Q&A, or the second Q&A...
|
Re: Team Update 1-15-2013
Quote:
If you're not sure it'll work, at least don't answer the question until you're clear. They answered related Q&As multiple times (I count 4). I'm not convinced enforcement is the reason behind this change. If anyone's interested, Q188 is requesting a rationale (as nicely as I could think of) for G23-1. We'll see how much trouble it gets me in--though they have offered explanations in the past. |
Re: Team Update 1-15-2013
Quote:
|
Re: Team Update 1-15-2013
Quote:
Note: Nevermind...just realized that Q188 is asking for rationale not giving one... *slapping forehead*... |
| All times are GMT -5. The time now is 23:19. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi