Quote:
Originally Posted by Vogel648
As a programmer I can tell you that doing much more than we did this year in autonomous would require more than 15 seconds and probably more time to program. Understand that there are ways of finding the light that don't involve spinning your robot in any way, but also don't allow for a full 360 of motion. Plus, again what if something is in the way, etc, etc etc. If we had another 2-4 weeks to do this, I would say, sure maybe we can get something worked out. But as a programmer, I know that when you say, "it'd be simple", really what you mean is that it seems like it'd be simple but it ends up being way more work that it was really worth.
Also, I don't really see much of a pay off of it being at the end.
|
This isn't anything you don't already have to deal with though. In both 2006 and 2007, other robots would actively attempt to block you, block off your vision, shake the rack, as well as knock you off course. Opposing robots would be aimed to hit you. That would be a point of failure of many autonomous modes, and would be one of the higher-level challenges for teams looking to make theirs more robust.
And I'm serious when I say "it'd be simple". The easiest would be to simply have your robot drive forward slowly for 15 seconds and have your driver pre-aim at the end of the match. It might hit another robot, but that's a problem in autonomous as it is now as well. For a bit more difficulty, make a simplifying assumption that the light will always be in view (if it is mounted where it was in Aim High, this wouldn't be a problem), and then you can do the slow spin and acquire. Much more difficulty might be to detect impacts and attempt to drive around them.
Here are some assumptions a potential autonomous-writer can make to make it easier, and removal of each of these bumps it to a higher-level
-There are no robots in my way
-The robot is pointed the correct direction
-There are no game field elements in my way
-I can ram into the end wall at low speed without damaging my robot
You don't have to make a autonomous mode that detects other robots and field elements, avoids them, and pirouettes it's way to the end zone. You can make a simple little one, and if your robot is not pointed the right way at the end of the match, just hit the e-stop before final autonomous starts.
If you look at 2006, there were several levels of autonomous:
-Drive-forward defenders
-Drive-forward, then aim again defenders
-Stay-in-place shooters that were pre-aimed
-Shooters that drove a little, then shot
-Shooters that could drive across the field, re-acquire the camera, then shoot
-Shooters that, while shooting, could detect an impact, stop shooting, re-aim, then shoot
IMO, lack of participation in autonomous mode this year was because it was simultaneously perceived as 1) not worth it and 2) very difficult. If you make it worth going for, then teams will, at the very least, make a drive-forward mode. Aim High had plenty of participation in autonomous, at least so far as the drive-forward modes were concerned.
The pay-off would be to have a mode that is at its base level slightly more challenging than drive-forward that isn't JUST drive-forward. Plus, real engineers have to deal with variability, why don't our programmers?