![]() |
Why the low Gear love
I'm seeing a lot of discussions on fuel delivery and scoring.
Some discussion on climbing Very little on delivering gears quickly. More worryingly, I keep seeing a misconception on the VALUE of gears. Given that one gear is given to you, in teleop only, the wrong values are: 1st rotor = 40pts/gear 2nd rotor = 20pts/gear 3rd rotor = 10pts/gear 4th rotor = 6.7pts/gear Many people are forgetting that the 4th rotor is actually: 6.7pts + 1/6 RP in qualifying, also remember that in the high goal 6.7pts take 20fuel In playoffs these gears are 23.3pts each. 40+100pt bonus. That's 70 fuel in the high goal for each gear or 420 fuel just for the 4th rotor. Time in two minutes: worst case (one robot) = 10s/gear best case (three robots) = 40s/gear For all the emphasis everyone puts on fuel as the tiebreaker, not many alliances will get 4 rotors going, even in playoffs. |
Re: Why the low Gear love
Quote:
I think fuel will become a particularly attractive scoring option if an alliance can score more than seven gears but fewer than thirteen gears (or who can accomplish the feat of scoring all 13 of their gears). It doesn't make sense to sink time into a scoring objective that won't yield any points*. *edit: assuming that the primary objective is to win the match |
Re: Why the low Gear love
I doubt we can do 5 or 6 or 7 gears on our own (and in qualifying, on our own is how we figure matches will go). So, the first three gears are worth 80 points in teleop.
Fuel....high goal....that's equivalent to 240 fuel, eh? I love the gears. |
Re: Why the low Gear love
One thing I think a lot of people overlook is how much the first rotor doesn't matter unless it is done in autonomous. If everyone gets the first rotor free, that means no one really got it free. It artificially raises everyone's score by 40 points. That being said, getting all four rotors will be critical in playoffs because of the huge point swing bonus. If at least two alliances can do that though, it's going to come down to everything else.
|
Re: Why the low Gear love
Quote:
Quote:
|
Re: Why the low Gear love
Quote:
Overall this does not negate the original post. Even the first 6 gears won't be achieved each time, but I feel mostly because of the low priority given to them in the robot design. Most teams so far seem content with just the mail slot approach, and leave the lining up to the driver. Given some focus, gears can be gathered and placed faster than people expect. |
Re: Why the low Gear love
I think the lack of Gear love comes from the fact that you can literally build a static box and score the Gear. Many teams believe that this box (I like to say Gearage) will be suitably effective when compared with an active mechanism.
I think I might agree... if you build a Gearage and you have 4 plus weeks to practice with it, aren't you going to be better off than a team with a complex active mechanism when they get less time to practice with it? There are techniques and drive maneuvers that we've already experimented with that makes a Gearage much more effective. While I agree that Gears are crazy important, and they're being overlooked by pretty much every low to mid tier team that's attempting Fuel, I disagree that you need an active mechanism to score Gears. I think a simple mechanism plus drive practice trumps a complicated mechanism with less drive practice. That goes for pretty much any aspect of FRC. |
Re: Why the low Gear love
Quote:
The 3rd and 4th rotor have pre-populated gears, at least until DCMP and CMP events. So you only need 1 gear for the 1st rotor, 2 gears for the second rotor, 3 for 3rd and 4 for 4th. Since there is the reserve gear that means that you only need to place 9 gears to start all of the rotors spinning and earn the ranking point. If you assume that at least one gear is placed in auto, and the reserve is used as soon as teleop begins the points are as follows. 1st 60 reserve 0 2nd 40 3rd & 4th 0 5th 40 6th-8th 0 9th 40 plus 1 RP Place 2 in auto and it becomes 1st 60 2nd 0 reserve 40 and then it follows the above schedule Place 3 in auto and it becomes 1st 60 2nd 0 3rd 60 reserve 0 4th 0 5th 40 and then it follows the 1st schedule. Which does point out why the gear conumdrum and why placing the 6th may be a waste of time if it is not done early enough to allow for 7th-9th to be placed and rotated before t=1 |
Re: Why the low Gear love
Quote:
Separately, I think Ginger is right. It's not often we have a direct scoring facet that is critically important but minimally mechanized. It's not that people won't be running gears. I expect to spend most of my time most matches running gears, but the investment is in practice rather than complexity unless you're at the level when you want one of the best gear pickups in the world (we're not). Think of gear scoring more like drivetrains. Everyone (almost) needs them, they're critically important, but we don't talk about them much. We could make the same arguments about endgames basically every year: "one climb is 50 points, and yet everyone keeps talking about fuel". Or, "climbing is only a couple dozen seconds, and yet everyone talks about it as much as gears". Importance =/= Match Time =/= Mechanization =/= Scoring Potential Quote:
|
Re: Why the low Gear love
As for value, it's all about how people envision the competition season will play out. Here is what I imagine are going through the minds of do-it-all teams based upon what I've read and heard*:
*I don't mean to imply any team who thinks these things is right, wrong and/or will have a bad season. Every team has to decide what's best for their team based upon the info they have and their team vision. These are simply a collection of what I've read & heard. I know that no matter what, my team will likely make a shooter for demos. These balls are really fun for kids. |
Re: Why the low Gear love
Quote:
Which means a fuel bot with the the simplest gear mechanism that scores 2 gears and 9 low fuel beats you. Auto gear gives you a +20 cushion so a fuelbot has to score 2 gears and 63 high fuel to beat you, but still. A robot with a passive gear mechanism, a successful "drive straight into the lift in front of you" auto and a fuel dumper is probably going to win a surprising amount of quals matches. Even more with a climber, which is looking rather easy. Unless you expect to be a quite efficient gear bot, you ignore fuel at your peril. |
Re: Why the low Gear love
There does seem to be a lot of peril in this game.
|
Re: Why the low Gear love
Quote:
Quote:
If your two alliance partners can score a single gear each, then you have to score 4 gears to contribute at all, and 10 gears to contribute more than 40 points. If your alliance partners score 3 gears each (on average) then you need to be able to score 6 gears to contribute at all. I believe that on average, the other two robots on our alliance will be capable of contributing between 1 and 5 gears combined. In matches where they can score no gears, a loss is likely anyway, if they can score 6 or more gears then a win is likely anyway. If we score a single gear in Autonomous, assuming the above is true (1-5 gears from others) then scoring anywhere from 0-7 gears is worth 0 or 40 points. if you can score 7 gears in Teleop then there is a decent chance you are only adding 40 points to your alliance score. If you could add those same points via the high goal then you would have the same odds of winning, but win or lose you would add a ranking point. This is the most interesting game since 2004 when it comes to specializing and team strategy. |
Re: Why the low Gear love
Quote:
|
Re: Why the low Gear love
One way to attempt to overcome the point values that Kevin rightly pointed out is to design a very efficient gears-only bot. A team that can consistently cycle rapidly and get three rotors turning on their own would do alright. This would require a ton of automation and driver practice, but I don't think that the only top-level bots we see will be ball shooters. Someone, somewhere is going to break gears.
|
| All times are GMT -5. The time now is 13:56. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi