|
Re: Programming goofs!
I guess I have a couple of moments to share. Both were pure awesome, both were goofs, and both differ in the amount of awesome of failure/win that ensued afterwords.
I'm sure I've mentioned this before, but for Breakaway, I attempted to urge our programming to just program a go forward autonomous code. This way, we could at least score in the near zone. The programmer did just that, and we ran out onto the field with untested code. The match starts, and the robot proceeds to drive backwards over both bumps and we manage to rip the bumpers off one of our alliance partners. The amount of failure was amazing.
Another goof was more recent, we had this bug in the autonomous where sometimes, our lift does not initialize (Our lift leans back, and we use two pneumatic cylinders to lift it straight up). In one such match, this just so happened to be one of the few before eliminations, this our cylinders didn't fire. The drive team and I watched as our chances of seeding high went through the floor because the tower pistons failed to fire. But to our surprise, the tower pistons fired at the beginning of teleop. It wasn't until later that I found out that one of our programmers had gone in and programmed a safety at the beginning of teleop. I was so proud of that programmer for being one step ahead. I equate that to giving Murphy's Law the finger.
Anyways, just a couple of goofs that have a space in my memory.
- Sunny
__________________
1261: 2007-2012
1648: 2013-2014
5283: 2015
|