![]() |
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
Maybe your saying make the Excellence In Engineering award qualify a robot to worlds too? |
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
And most of the times judges don't get to watch many of the matches. |
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
Code:
Points Team Selection Finish AwardsWinners: 303 (prequalified, Mount Olive Chairman's), 2590 (Montreal Winner), 3340 CA: 1923 (prequalified, TVR EI) EI: 3314 RAS: 5666 Generating 3 wild cards: Current System: 11, 193, 1257 District points: 11, 193, 4285 Looking at the OPR for that event, 4285 averaged ~43 points per match, and 1257 ~21 points per match. Using district points for wildcards sends a slightly different but more competitive set of teams to CMP. |
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
And I just said "That's the point." Having judges do what they do isn't about objectively determining who the "Innovation in Controls" award winner should be- it's about exposing industry leaders who are often judges to these amazing students and exposing these students to industry leaders. Ex: I talk to Team A and Team B, and Team A's students tell me in detail about their sloppy control system for their mechanism, while Team B wins the regional with their tightly and highly controlled mechanism but can't discuss it with the judges. I, as an FRC person who understands what these students are doing, might still award the award to the winning team, whereas an outsider judge will award it to the team who can talk about what they built better. That is (I think) an intentional part of the system. I place more focus on results, whereas a non-FRC person will place more emphasis on the attempt and the innovation than the results, while also learning about what FIRST-er's do. I think the main problem with the regional system is when finalists aren't invited to championships or when the second best robot at an event loses in the semifinals because they were on the wrong side of the bracket or something. What if (bold idea), before week 7, FIRST polls a number of experts on who the best 20 or so teams to not make championships are (kind of like this, but two weeks earlier) and invites them to the championship event. |
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
1) FIRST polls experts on best 50 teams to not CURRENTLY make championships. (Trust me, there's a reason this number is so high.) This happens sometime around Week 6. 2) FIRST looks at who still has a chance to qualify (playing Week 7, maybe playing Week 6), or is near the top of the waitlist. These teams are set aside. 3) FIRST looks at geography and representation. Teams from underrepresented areas get higher priority than teams that are from fully represented areas. 4) The combined "best teams" and "underrepresented areas' teams" sorts determine the order of offering--but only to the top 25 on the combined list. 5) After Week 7 plays, the list is revisited. The bottom 25 and the teams that were set aside are now eligible for invites. |
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
|
Re: [FRC Blog] Frank Answers Friday: Championship Slots
Quote:
Any sort of equal representation system based on region will do this, and that's (I think) an unavoidable problem, albeit a lesser problem compared to how championship slots are currently allocated to regionals. |
| All times are GMT -5. The time now is 11:38. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi