![]() |
[FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
The Scoring system has a built in limitation on the number of Matches that can be generated. From the manual:
"For the following Event types, Limitations have been set in the Scoring System to a maximum of 5 Matches. In addition, the cycle times (time between Matches) will automatically be no less than 7 minutes: League/Meet League Championship Qualifier Championship Anyone know why? We can put 6 to 8 matches into our events easy and think it gives teams better results. Thank you, |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
I haven't seen it offically anywhere, but I heard FIRST wanted to promote parity between events in different regions, hence the limitations. Here in MN, I believe the plan is to run 3+ practice matches before the official matches for teams.
Personally, I'm a fan of letting regions decide how many matches teams get over a certain minimum, but then, I also am a fan of actually giving teams feedback and we know how FIRST feels about that. |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Our region wants to standardize on 6 matches per team. The program can do it in "Scrimmage."
Does anyone know what changes if set the event to "Scrimmage?" Are there any limitations in the program by using it this way? Thank you, |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Quote:
|
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
You could always run the amazing VEX Tournament Manager software. Everything is a user parameter you can set. I've run 32 team events with 4 fields and have gotten 10 plays per team in before 2PM (with a lunch break).
We do pre-warn teams about quick turn times and they need to manage their battery collection. We also have spares and extra chargers on site. High cost of the robot, high cost of the entry for the event, transportation, food and only getting 5 plays seems like pretty bad value proposition. |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
What effect will a low match count have on the integrity of the rankings? Are there any statisticians in the crowd that can run quantitative data showing the relationship between number of seeding matches and accuracy of rankings?
Five matches seems a bit on the low side for accurate ranking. Though running extra practice matches is better than nothing I suppose. If the issue is event consistency vs. event quality my opinion would be that inconsistent numbers of matches between events is the lesser evil compared to artificiality limiting all events. Allison Edit: I recall within the past year or two a post in an FRC thread showing the difference in noise in the rankings at 6 vs. 8 vs. 10 vs. 12 matches. It may have been one of the district vs. regional discussions? Anyway, tried to search but it's lost to me at the moment. |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Quote:
|
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Quote:
|
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Quote:
Nah. Certainly not without an agreed enumeration of expenses and results that can be assessed to determine both value, and barriers to entry. The skills, tools and techniques you named can all be taught, used, and improved in VRC (and any of almost all other STEM programs that build things). "... students in more customizable programs learn a lot more" Nah Students in all programs can learn what they are taught. If a student I am helping doesn't learn something they want to learn, I blame myself, not the program that happened to bring us together. "... and in turn become more inspired." A) Nah B) We determine this how? Do we weigh the students at the beginning and end of a season, to determine how much inspiration they absorbed? Do we measure their lung capacity, because "inspiration" can refer to breathing? Do we normalize the results by the number of students reached, or by the dollars the students can afford to invest in the program/team/robot costs? This is a sore subject for me. FTC, VRC, FRC, and ... are all tools that all need to be used well. It's a poor craftsman who blames his tools. Lets go back to the original topic. Blake |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Didn't say switch to VEX said, run the Tournament Software, it runs lots and lots of matches.
Quote:
I'm a fan of all robot programs, just wished there were more roboteers in them. |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
I have posted a question asking for some reasoning to the FTC Scorekeepers forum, and will keep you all posted if I hear anything back and am allowed to share.
|
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Crazy, we only have 12 teams at an event so only ~2 hours of matches??? a little ridiculous.
|
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Quote:
Anyone know where on the public FIRST forums we can discuss the Scoring system and other Tournament related questions? Maths222 - Why would anything about the scoring system be private conversation? Without the Field Control System, Scorekeeping will be the central position of the event. We need to understand as much about it as we can. FTC has been showing wonderful increasing transparency by posting all the volunteer documentation for the last couple of years. Just a few of these areas remain a mystery. I hope they continue to open up the transparency and let everyone in on the shared knowledge of these hidden forums. |
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
We learned here that if you choose your event type as super regional you can run as many matches as you like, no ill effects on rankings or scoring.
|
Re: [FTC]: Scoring Program Can't Schedule More Than 5 Matches per Team
Quote:
|
| All times are GMT -5. The time now is 17:01. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi