|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#1
|
||||
|
||||
|
Should we rebuild our robot to be an autonomous container grabber?
One of the teams I'm working with this year is considering switching their robot to an autonomous container grabber if they qualify for the championship. The "robot" would be four container grabbers. I don't want to disclose the exact strategy, but let's just say they have a good chance to win almost any container grab competition.
At first, I dismissed it as crazy. Sure, containers from the step are important, but can you really justify picking a robot that can only do one thing? After autonomous mode, the robot doesn't move - not the most exciting thing ever. A few nights ago, a student and his brother came to me and explained why they thought it was worth it. They would only make the change if/when they were at the championships. After watching teams play, it's clear that a good team can make two full 42 point stacks. It's not unimaginable that two of these teams could end up together on an alliance at the championship. If these teams each scored their two stacks, and we grabbed the auto containers, the other teams would have to stack 21 totes to make up for our fourth stack and tie with us. It gets even better if the other two teams score more points. I was worried that this alliance might not make it out of quarterfinals, but the four team alliances would let us sit out and the other three bots rack up points to boost our average. In semis, we'd score fewer points, but we'd severely limit the number of points our opponents can score. What do you guys think? Is it worth it, or are we just crazy? How desirable is the ability to be amazingly good at grabbing center containers? If we're the best at it, are we sure to be picked? |
|
#2
|
|||
|
|||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
It's a viable idea, but don't forget,
R17 At an Event, Teams may have access to a static set of FABRICATED ITEMS, not bagged per R14, known as the WITHHOLDING ALLOWANCE, that shall not exceed 30 lbs. to be used to repair and/or upgrade their ROBOT. The WITHHOLDING ALLOWANCE may only be brought into the Venue when the Team initially loads in at the Event. Items made at an Event do not count towards this weight limit. |
|
#3
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Quote:
|
|
#4
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Can you post a before and after pic like they have in dietary commercials?
|
|
#5
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Perhaps more relevant:
Quote:
|
|
#6
|
|||||
|
|||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
If you're going to make such a drastic change on a Thursday, I would definitely want to have already built one so you don't have to do nearly as much tweaking at competition.
Also, if you're going to tune for the autonomous container grab, you should consider:
|
|
#7
|
|||||
|
|||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Quote:
|
|
#8
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Assuming your container grabbing ability is top-notch, and you grab all four containers every time, you alliance needs to make either 7 fully capped stacks of 5 or about 5 fully capped stacks of 6 to "beat" an opponent.
So yes, the top two robots in a division are theoretically capable of this, but will your ability to outscore your direct opponents be able to keep your average score high enough to move on to the finals of playoffs where it really matters. However, if your options are a mediocre stacker or a potential clutch pick at the championship event (even as a fourth robot the alliance just brings out for finals), I'd take the clutch pick personally. I hope to see this robot happen. |
|
#9
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Very true. Most teams at champs go to three events, that is 90 pounds. If you were pre-qualified or otherwise confident in your ability to get to Champs, you can strategize by bringing 30 pounds of fabricated items at your first two events with the express purpose of just putting them in the bag after the event is over. You make duplicates of whatever you are fabricating to go in the bags so you can test it while it sits in the bag (likely in your shop). By champs you have 90 pounds worth of assemblies ready to go.
I imagine teams with little raw talent on their team but with high aspirations might even wait a couple weeks to see mechanisms they like, deploy crucial ones to win their regional and qualify for champs, then build the other crucial stuff to split between the bag at their second event and champs. We actually switched out almost 100% of our robot last year between stop build day and championship Saturday. (but we still need stop build day, right?) |
|
#10
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Quote:
148 almost put up 5 stacks on their own in the eliminations at dallas (in week 1 mind you), except one of their stacks took a tumble transporting it. I'm willing to bet they practice more and fix any issues they have and are capable of doing 5 stacks consistently in the future. If all of those are topped with a bin and litter, most likely the best the other team can do is tie them by matching them. (The other team wins if they have an additional stack of any size). So say you're in 148's shoes on Tesla and finish qualifications and are seeded first. I would choose the team that can grab 2 or 4 middle bins the fastest then pick the best landfill stacker. So, for whatever team is considering this: if you already have a spot at worlds, I think it is a very viable game plan. You better hope you are one of the fastest robots that can grab those bins though. You won't seed very high most likely, but the teams that will be alliance captains will take full notice of your potential for them. |
|
#11
|
|||||
|
|||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Quote:
|
|
#12
|
|||
|
|||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
Quote:
Edit: I see you corrected it. But still how is the 30 an advantage for multiple event bots. Just for swap outs? Last edited by Boltman : 04-03-2015 at 00:18. |
|
#13
|
|||||
|
|||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
I think this year is going to see a lot more rebuilds than in the past. We are rebuilding our robot completely at our first event. Don't get me wrong, I don't think we will be good this weekend after the rebuild. Our original design wasn't going to cut it and we need to find a way to be better by our next event, championships, and in the off-season. In other games you can play defense or have clever game plans. In this game there isn't much hope for that other than the center cans and by worlds I'm pretty sure the fastest RC grabs are going to be on some of the very well known teams. There will definitely be places and ways where other teams can contribute but it's going to be interesting to find them.
|
|
#14
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
The funny thing is that they most likely won't seed every high either. I could easily see the fastest RC grabber in a division be in the bottom 25% seed wise, but be first picked in alliance selection.
|
|
#15
|
||||
|
||||
|
Re: Should we rebuild our robot to be an autonomous container grabber?
gg. You can if you want. From disassembling an OTS gearbox all the way up to bringing raw stock and knowing what you need to cut, it's simple to cut down a change to 30. It just keeps getting simpler after that (simple doesn't mean easy, but it can).
Quote:
Obviously there are drawbacks to this (you don't allow yourself to make any spares unless you play smart, you spend practice day reassembling, you don't spend your allowance on making iterative improvements to your existing designs) but there is enough play in the rules to do it. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|