|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||||
|
|||||
|
2010 Lesson Learned: The Negative
What could have FIRST done better this year?
|
|
#2
|
|||||
|
|||||
|
Re: 2010 Lesson Learned: The Negative
NO GAME OBJECT IN THE KIT OF PARTS!
FIRST never do this to us again! The surface finish on the balls was so specific at driving the design of ball handling mechanisms and you screwed it up again by chosing something we couldn't get and not warning the manufacturer to stock up because a huge influx of orders would be coming. |
|
#3
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
Truthfully? As far the game goes, my only REAL complaint was the DOGMA system. Ok idea, bad implementation. Should have been 1 point penalty once per ball, not repeated penalties.
|
|
#4
|
|||||
|
|||||
|
Re: 2010 Lesson Learned: The Negative
Peter and Tom just addressed #1 and #2 on my list.
I would like to see a stronger incentive for using the camera (and autonomous mode in general). The Classmate is at best a work in progress. Between Windows startup times and power management woes, battery life, USB enumeration issues, powering the USB ports, cheapo Ethernet ports, and the tedium of "FMS Locked" and E-stop, I think we can do a lot better. |
|
#5
|
|||
|
|||
|
Re: 2010 Lesson Learned: The Negative
This wasn't completely FIRST's problem, but the discontinuation of the WGA bridges and their replacement with the WET bridges was a bit of a problem that could have been avoided by some more testing on FIRST's part to make sure there weren't any major problems with it (long connection times, disconnecting WGA bridges, etc.)
EDIT: agreement with most of the stuff with the classmate on the above post |
|
#6
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
Quote:
|
|
#7
|
|||
|
|||
|
Re: 2010 Lesson Learned: The inspectors
Ok first of all i'm going to say i appreciate all the volunteers that helped out with FIRST FRC robotics this year and every year, but i think that FIRST needs to have a code of conduct for when it comes to inspecting a teams robot. For example having to ask to move your robot at ANY and EVERY time they wish to do so, ect. the reason i say that is because this year when we went to Atlanta we missed our very first match because during our teams inspection the inspector moved our robot while it was off while this doesn't seem like a problem it is because our team decided to use CAN this year and when he moved our robot he sent reverse current into our jaguars thus completely ruining functionality of 3 of our jaguars it was to bad that the only thing the texas instruments guy could do for us was give us three new jaguars(after 30min. of trying to fix them. on top of the at least 1 hour inspection) and after that things just went down hill for our team.
|
|
#8
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
I didn't like the many field problems experienced at the competitions. Sometimes matches get delayed for 10-20 minutes because of these problems. The Kettering District competition lasted until 7:00PM because of the many field issues that needed to be worked on. I know the system had to be rebooted a few times, but each of those reboots took up to a half hour each! FIRST or National Instruments needs to find a way to make problems like these quicker to solve and fix to make things run smoother.
I also didn't like how it is hard to figure whether or not it is a field or a robot problem when a robot doesn't run during a match. There needs to be a system in place that determines functionality of both the field and the robot to better determine where the problem is coming from. Last edited by The Cyborg : 19-04-2010 at 17:23. |
|
#9
|
|||
|
|||
|
Re: 2010 Lesson Learned: The Negative
I didn't like that we have to reuse control systems from a previous year. *thinks about the pile of robot skeletons in the closet*
I didn't like the no-bonus autonomous. I didn't like the low scoring matches. I didn't like how the game wasn't conducive to defense. |
|
#10
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
I dont like the seeding system. Although, next year, with a new game, I hope for a new seeding system more like elims.
EDIT: Suspension. With only about 5 total in the season, it was a completely failed game mechanic. Last edited by Grim Tuesday : 19-04-2010 at 17:30. |
|
#11
|
|||
|
|||
|
Re: 2010 Lesson Learned: The Negative
It looked to me like some robots at the championships had issues (weight, electrical, pneumatic) that needed to be fixed but passed inspection at the regionals. I don't think they're doing teams a favor by letting them through regionals this way. Maybe they can issue conditional inspection approvals to let teams compete but all issues need to be corrected before the eliminations. That way teams earning their way to Altanta would be confident they are good to go.
|
|
#12
|
||||
|
||||
|
Re: 2010 Lesson Learned: The inspectors
Quote:
As far as robot inspector code-of-conduct goes, the inspectors at CMP were presented with a huge challenge: get 340+ robots inspected in less time than what is allotted for most regional events. If your inspector seemed a bit rushed, it's because we all were. If you felt uncomfortable moving your robot, you should have said so. I will only touch a robot when looking for sharp edges, tracing wires, or inspecting bumpers. If someone asks me to help support their robot, hold a component, or move a mechanism, I'll do it because I trust the team will not ask me to do something that is unsafe. No inspector would ever want to damage a team's robot. We all want to see everyone compete safely and within the rules. |
|
#13
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
A picture paints a thousand words. Here are two pictures that express my biggest negative this year.
There was a lot of this........ ![]() shortly followed by a whole lot more of this........ ![]() Hurry up and wait....and wait....and wait....... Maybe we can have custom built for FIRST WiFi next season. |
|
#14
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
Sort of a follow up to the DOGMA issue before. It was a real problem when a ball would fall off the ball-return track (before passing through the counter) and a reset-volunteer would pick it up and place it back in the mid field (A rare occasion, but I still saw this happen more than once). This obviously potentially would ruin a match for the alliance. So my suggestion would be better volunteer training for those special cases as described.
|
|
#15
|
||||
|
||||
|
Re: 2010 Lesson Learned: The Negative
Quote:
I also don't think teams should be held off the field at regionals for minor discrepancies, but the teams should be forced to correct such problems before the elimination rounds. The pre-elimination round weight check should indeed include a check for any conditional "passes" and verification that the problem(s) are resolved. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 2010 Lesson Learned: The Positive | Koko Ed | General Forum | 37 | 21-04-2010 16:42 |
| Lessons Learned - The Negative | Koko Ed | General Forum | 221 | 25-04-2009 16:40 |
| Lesson Learned: The Negative | Koko Ed | General Forum | 98 | 07-05-2008 20:32 |
| Lesson Learned: The Positive. | Koko Ed | General Forum | 24 | 21-04-2008 13:11 |
| Lessons learned 2005: The negative | Koko Ed | FRC Game Design | 138 | 06-05-2005 18:58 |