Team Name: Woburn Robotics.
Team Number: 188.
Number of people: 19 (29 with graduate and teacher mentors).
Male: 10; note I am the only grade 12 male on the team, (or Senior as you Americans like to say)
Female: 9.
What everyone does:
This could answer that. It's what everyone officially does, though there's a lot of crossing over.
Time to design various things on robot: About two days per function, but this is involved with prototyping; once we decide what to do, design
is prototyping.
Prototyping: Heck yeah. Very little CAD either.
People who design things: A very small minority, should be bigger.
People who build things: Often the same minority, with one or two who can be instucted to do things. This should be much bigger, at least 12.
Hours per day people put in toward the robot: On average 2, but this ranges from about 1 hour to 6 hours. Note that people might be around or working on something different and not count toward this number.
Mentor makeup: On occasion we get some drop-ins from helpful engineers, but it's mainly teacher mentors, graduates, and students.
Driver experience: As driver this year, I already could drive a robot well and practised a bit on an old one in build. I've also been (the best) human player before so the whole drive team aura wasn't new. The operator didn't have any experience but didn't really need much.
Experience on the robot: Barely any going into Pittsburgh because of delays; we try to have three to five days of solid driving (which never happened this year), but next year we will choose a drive team very early and have them practice whether or not the robot's done.
Design methodology: Generally we try to design one specific function really well and work off of that strength. This year we made an everythingbot, and it paid off (you'd think we'd win a regional).
Coolness on robot: I got your coolness right
here.
Work on auto mode: A whole lot of work was done in this area and a lot of learning. Our insanely sophisticated guidance system didn't work because (among other things) the IR beacon was weak.
Autonomous: We use dead reckoning/timing to get around now. A few very simple programs.
Speed: 17fps
Robustness: 8 (5 is average)
Agility: 7 (5 is average)
During the competition, did you feel that your alliance partner let your team down in some way?
Yes ("OMG!!!11one," says the typically goodie forumgoer, "that's not GP!"), but we're guilty of it too, as are you, as are you. Nobody is angry because that's how it goes. I can just see people reading into this statement too much.
Did you let your alliance partner down in any way?
In at least three matches I can think of right now, one of which we won. Three matches is good in anyone's book I think. By the way, mechanical failure counts as letting down in my eyes, in addition to drive team error.
Where were you seeded before the finals round started?
Top 8 in Archimedes and Canadian, but not so good in Pittsburgh.
Did you win any awards during the competition?
Yeah.
*Sportsmanship, two individual awards for mentors (WFA, VOY), and Website Design at the Canadian Regional.
*Website Design at Pittsburgh.
*Website Design at Championships (booyeah).
What is your name?
Jonathan Lall
Age?
17
How long have you been on the team?
3 years, and counting.
What was your role on the team?
This year I was President, Driver, and Webmaster. The Franchise.
"Jonathan Lall is the Chosen One; the prodigal brother who will bring balance to Woburn Robotics." -former team member in my first year.