|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#31
|
||||
|
||||
|
Re: Defense v Offense
It's quite possible to add a little metal, some nuts/bolts, an electronic controller or two to the KOP in order to derive a mechanism that scores on the lowest row. Thus even the defensive robots can score something if their alliance partners cannot. That the defensive robot team doesn't have the foresight to do so shouldn't reflect negatively on other teams who choose whether or not to play defense or go offense.
Just thought I'd throw that out there. |
|
#32
|
||||
|
||||
|
Re: Defense v Offense
Quote:
Quote:
I might be wrong, but this just means you can't steal it from them. I don't see where it says you can't knock it out of their manipulator as long as your intention is purely defense and not to take possession of the game piece. Last edited by Molten : 10-01-2011 at 21:39. |
|
#33
|
||||
|
||||
|
Re: Defense v Offense
Quote:
In my opinion, you rarely, if ever, set out and build a defensive robot (unless your team is incapable of building an offensive one). The best defensive robots typically are from teams build an offensive robot, but their scoring mechanism isn't up to par. The best defensive robots typically have great drivetrains and drivers, which is also a key for strong offensive robots. So, why not build an offensive robot with a good drivetrain and play defense as a backup? |
|
#34
|
||||
|
||||
|
Re: Defense v Offense
After our strategy meeting today, our team decided to make a defensive robot. We'll have to see how it pans out, but as I see it, we could score on the two lower racks, if forced to, but our main strategy is to block other robots from getting their game pieces, and stealing them from their human players throwing them in.
Another concept based on where on the field we are is to "punt" gamepieces to our alliance partners, who can in turn, score them without having to traverse the field. |
|
#35
|
||||
|
||||
|
Re: Defense v Offense
Quote:
|
|
#36
|
||||
|
||||
|
Re: Defense v Offense
Quote:
|
|
#37
|
||||
|
||||
|
Re: Defense v Offense
Quote:
My point is that you rarely see a team that just planned to be a box bot be an amazing defender as its usally a traditionally good team that stuggles with their manipulator. 171 at Wisconsin was a perfect example of this last year. Although they planned to be a scorer, their kicker and lifter weren't quite perfected so they were smart enough to adapt and play to their strength, which was defense. Their strong 6 wheel drive shut down Wildstang in the semifinals. They did drastically improve their scoring, but they won a regional because their smart drivers and strong drivetrain allowed them to play fantastic defense. |
|
#38
|
|||
|
|||
|
Re: Defense v Offense
I had a great defensive strategy and design all made into a powerpoint. Apparently I couldn't present it because we will never go defensive. I mean I got shot down without even being asked the design or strategy. I honestly think it is genius but no one would listen. I emailed my mentor if I can even try convincing the team in 10 minute presentation. My argument for being a defender this year is that we were never really successful as an offensive robot ever in history. I still get the vibe that we are a rookie team. No one is ambitious enough (even though mentors think its too ambitious) No unique ideas ever come out of the discussions. The most unique ideas are the ones most criticized. Personally I get the vibe from everyone that I am annoying and talk too much. Hell thats a lot better than sitting there and not saying a word. I say if you have an idea let the world know and not complain later. One thing that is held against me all the time is that its all ideas, so I actually tried CAD this year. Its not good but hey its worth a try. I spend 6 hours working and developing my idea and no one listens with an open mind; I am sick and tired of that. Apparently I am pushing my "agenda" too aggressively.
Adding onto that, I am the lead programmer this year, and most the programming group is either my age or older. Now I do not think they respect me enough to just stop talking and listen to what I am demonstrating. You know honestly I can program the whole robot in whatever fashion I want, but for the sake of others, I chose to program in Java instead of C++ (I wanted to try inline Assembly) Now the programming mentors can't show up most of the time, so they trust me as a leader, so I am kind of like a mentor too. I feel that the software group never has a say in my team. Its like "programmers, can you do x and y for us?" We are the bottom apparently. Now they do not trust me or my group to do a fully automated robot either. It was not my fault that the autonomous mode last year was pretty much programmed AT the competition. Everyone said don't worry about autonomy until a day before shipping... Now I was a rookie that year, they expected a functional autonomous mode with just an IR sensor. And at the matches they blamed me for running into the wall or missing the ball. Just great... So my mission of a fully autonomous robot is out the window (we can't even afford the sensors needed) /rant Honestly, I think that was why I played Madden all day in the pits last year... |
|
#39
|
||||
|
||||
|
Re: Defense v Offense
Quote:
Im sorry to hear that your disappointed, but neither Chief Delphi, or this thread is place to hear your problems. Bring them to your teacher, or other mentors. I have heard from our programmer that it is very possible for an autonomous scoring mechanism during tele-op. However, what I think is really interesting is this defensive powerpoint. Since our team has decided on a defensive strategy, I dont suppose that you would be interested in sharing this powerpoint with CD? It could be quite eye opening for some teams. |
|
#40
|
|||
|
|||
|
Re: Defense v Offense
Quote:
|
|
#41
|
|||||
|
|||||
|
Re: Defense v Offense
Quote:
So while they have no choice to do anything else but play defense they'd best be careful where and how they play defense this year or else instead of preventing the opposing alliance from scoring points they end up costing their own alliance significant points. |
|
#42
|
||||
|
||||
|
Re: Defense v Offense
Quote:
In 2007, Team 48 never intended to have an arm/manipulator, just a purely defensive robot with a very strong drivetrain and ramps to hold two robots. It was definitely one of my favorite years, so I'm looking forward to this season. I agree with the idea of a strong drivetrain coupled with a decent hanger may be the way to go. I also think speed, whether used for offense or defense, is going to be important this year. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|