|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: "Random" match Schedules
Quote:
One other thing relating the perpetual opponents to alliance captains is, it is impossible for both teams to be alliance captains. Your record is the inverse of your perpetual opponents record. you cannot possibly both be alliance partners, which is unfair to two really great and worthy teams who just so happen to be numerically close. my team, we play every match against the same team. the bad thing is that the one downside of our robot is its traction. we have omniwheels and they arent gripping well. all of our opponents mechanisms arent functional so they have to focus on defense. we keep getting alliance partners that cant tube like we can so our opponent just slams us every time we pick up a tube. by the 5th match however, they received a yellow card (if not the first at the regional then definitely the second) for excessive violence. now we play an unagressive/paranoid partner for the rest of the matches which is too much in our advantage in my opinion. while i see what FIRST is trying to do, i really think that a purely random schedule would be the best, getting paired with whoever you get paired with, assuring the variety you expect. |
|
#2
|
|||||
|
|||||
|
Re: "Random" match Schedules
I'll have to agree with Karthik. The seeding is very important for ranking atleast the top 8 teams. A veteran #2 seed that has played and beaten all the other veteran teams at the regional with a rookie #1 seed that has barely beaten all the other rookies at the regional... That's just asking for trouble.
In addition, I can't see how a rookie team would prefer to be paired with and against other rookies for an entire regional. Many of these rookies were planning on being enabling robots to leverage the ramps and other features of veteran teams. Basically telling them that they'll never be paired with a veteran team just because is not a nice thing to do. Mostly, I'm just surprised because the only serious complaints I've ever heard about the alliance pairing algorithms were that teams had to play with or against another team for half a regional or so. I can't really understand why first would turn around and go with a system like this in the face of that feedback. |
|
#3
|
|||
|
|||
|
Re: "Random" match Schedules
All this discussion about Richards idea that this type of seeding rounds was a new approach by FIRST to level the playing, or that this was planned by FIRST, is simply wrong. When this happened at the scrimmage in Suffield, CT 2 weeks ago, it was discussed with 3 high level people from FIRST.They all agreed that what happen that day, and whats happening this weekend, would be corrected by the 1st week events. With all the other fixes that came out of the scrimmage, I guess they ran out of time.
By continuing this line of discussion you are giving FIRST, and the software people an excuse for not fixing something that needs fixing. Has anyone else notice that Mr Lavery his not added his voice to this discussion. Last year he was all over Hatch for every little issue. |
|
#4
|
|||
|
|||
|
Re: "Random" match Schedules
I don’t think they should even try to fix it. Why should the first week teams have to be the guinea pigs? Why should teams attending only the first week events end up having a less rewarding experience than ones who picked week four or five? This is an issue that could have been resolved way before the first event. I’m reminded of last year’s first week debacle with the scoring system and automatic scoring hardware. Not much changed in five weeks. Milwaukee probably had as many or more re-starts than VCU. They were still human counting in Las Vegas. It was not until the Championship that they programmed a break after autonomous - so they could at least get the autonomous winner right! Not much changed, except that we learned to live with it and made the best of it.
But last year had a really great game to make up for the warts. IMO, this year’s game is not as good, not even close. Whether the total experience is enough to make up for [insert pet peeve(s) here] remains to bee seen. |
|
#5
|
|||||
|
|||||
|
Re: "Random" match Schedules
The biggest problem I see with the perpetual opponent is simply the issue of an actually enemy appearing. In previous years there have been slight rivalries etc but by having a team that you play over and over ruins the atmosphere that we, or at least I love about FIRST regionals, a team could be your enemy one round then your ally the next. Without that I think teams can begin to get bitter towards each other, and whatever team ends up playing the number one team every match ends up being last just because of that it really adds too much negative competition into the game.
|
|
#6
|
|||
|
|||
|
Re: "Random" match Schedules
I personally think instead of having a 'if i cant have it nobody can' attitude one should have a 'well, at least everyone else will have fun' attitude. The people in the first week got the short straw, yes. but this cannot be changed; it already happened. i would hope that first will learn from its mistake immediately and try and make it so everyone else has the best experiance they can.
|
|
#7
|
||||||
|
||||||
|
Re: "Random" match Schedules
Quote:
Company X just started selling their 2000SUX sport utility vehicle. The first thousand SUX's on the road have airbags that deploy when the radio is tuned to 107.9 MHz, causing major accidents and injuries to the vehicle occupants. There is a public outcry calling for Company X to issue a recall and fix the problem IMMEDIATELY. The Company X CEO, nose firmly jammed north of horizontal, issues a statement declaring, "Oh, sorry, it wouldn't be fair for the first 1000 buyers if we fixed the problem for everyone else. You're just going to have to live with it blah blah blah blah blah......" I'm pretty sure the first 1000 buyers would be more appreciative of Company X AND WOULD MORE LIKELY CHOOSE TO BE REPEAT CUSTOMERS if Company X admitted the problem and did everything they could to repair the defect. Jack, I certainly hope FIRST doesn't follow Company X's lead. I expect them to be proactive. If they can't figure out a solution to this problem, then I'd hope they are willing to keep an open mind and consider outside algorithms brought to them by established members of the FIRST community, pride or contractual obligations or whatever be durned. Otherwise, I'd fear a significant increase in the risk of their "customers" taking their business elsewhere. This is a major problem - a "design flaw". Let's correct the problem so our customers are more satisfied with the product. Last edited by Travis Hoffman : 03-03-2007 at 08:51. |
|
#8
|
|||
|
|||
|
Re: "Random" match Schedules
Quote:
Please note that this problem was seen and pointed out BEFORE these regionals. This seeding in unimaginative and damaging to the spirit of the game. If it is the result of someone's "policy" they should take a close look at what they have created. From what I am hearing here it is damaging the experience of many teams this weekend and should be changed for TODAY'S matches. |
|
#9
|
|||||
|
|||||
|
Re: "Random" match Schedules
I carry a really 'mix' opinion on this issue. May be for some teams going against the powerhouse teams; its going to be a big issue, while for others it might sound right.
For my own personal experience, it has showed kids (especially our team) the spirit of GP. 612 is going against 611 in every single match. Their pit is right beside us. Even though both teams are going against eachother in every single round, they've been helping eachother throughout the competion. This example emobodies the true meaning of FIRST, Gracious Professionalism. Imad |
|
#10
|
||||
|
||||
|
Re: "Random" match Schedules
Has FIRST missed the mark? Part or the excitement to watch as a mentor is how the kids learn to stratagize with and against almost every team at a regional. While the mix for who you are paired with seems fairly random, having one team that you are always against is bad. Other than really getting to know that team very well and being able to easy tell your new alliance partners how to defend against them I don't see it having much benefit. I much prefer an offensive match and this looks like it will breed defensive matches. From what I have seen, simply pushing a robot around near the rack makes scoring ringers almost impossible. Veteran vs veteran and rookie vs rookie, what's up with that? There have been extremely competitive rookies and veteran teams that have had less than impressive years. All beit, a few power houses can always be counted on. Speaking of that, how many teams are looking at the teams attending thier own regionals today to see who they will be paired against. I know I did. First two listed vs eachother, Second two vs. eachother (At least that is how it goes at VCU)? The more random the better. You should be able to test your skills with and against as many teams as possible. This just doesn't measure up.
EDIT: I looked at the information available from NJ, STL, PNW, VCU. No match results were up for BAE. At PNW and VCU it looks like the first two teams listed are vs. each other every match. At NJ and STL it looks like the first two teams listed are vs. eachother every other match. I/We should all know more once today's matches are posted and when/if anyone has time to analize all the information. Last edited by ALIBI : 03-03-2007 at 07:03. Reason: Looked at team lists for all five regionals played. |
|
#11
|
|||||
|
|||||
|
Re: "Random" match Schedules
Add to your VCU list that 435 played against 510 every round. I could probably double your list of reasons that the current matching system is a bad idea, but if FIRST is already planning a change then I won't bother.
Can anyone confirm that FIRST is changing this for the next round of regionals and for nationals? |
|
#12
|
|||
|
|||
|
Re: "Random" match Schedules
We (1279) played against 1218 every match in NJ. (100%) Very non-random, and I hope this is corrected.
Last edited by Dad1279 : 03-03-2007 at 16:54. |
|
#13
|
||||
|
||||
|
Re: "Random" match Schedules
I could see how this whole thing was a plan by FIRST to make the competition a little less harsh to newer teams. However, as a few people have already mentioned, team number is not a measure of how good a robot will be. Hence, the plan backfired.
I think the problem needs to be fixed for the coming week's regionals, if nothing else go back to last year's system. Can ANYONE confirm or deny a plan to change the system for the coming weeks, has anyone been told anything? |
|
#14
|
|||
|
|||
|
Re: "Random" match Schedules
Not random, EVERY, and I literally mean EVERY game we played had at least team 948 (They became the number one seed). Because of these "random" match schedules we ended at the opposite end of the rankings.
|
|
#15
|
|||||
|
|||||
|
Re: "Random" match Schedules
Let's not contribute too many opinions on what was in the minds of the committee who designed this algorithm.
I don't think anyone consciously said, "Let's put vet against vet and rookie against rookie." Rather, the "max time between matches" constraint was emphasized over all other constraints. Then they simply decided on team number as a primary sort - they could have done it alphabetically, or could have done it randomly. It wouldn't matter. Once "max time between matches" was decided as having priority, teams would end up seeing the same teams over and over again. The popsicle stick in a bowl thing can easily be set up as a computer simulation. But then we have decided that "randomness" is the highest priority, and time between matches means nothing. Teach the computer could to do a popsicle stick picking. For Round1, totally randomize it. To pick for Round2 make a constraint that there has to be at least "X" matches before a team must compete again. "X" would vary based on the number of teams in a regional. It should be at least 3, but in the larger regionals could be 4 or 5. To pick the first X matches in Round2, the popsicle sticks of any team that played in the last X matches in Round1 would be set aside. Once the first X matches are picked, all the remaining popsicle sticks are thown into the drum, and the rest of the matches of the round can be drawn. Repeat for all matches up to lunch time. Then totaly randomize again, and finish Friday - or maybe set the X constraint for the first match of the afternoon to 1. Totally randomize again and pick for Saturday. This wouldn't work as well for the small regionals of 36 teams or less, because it would effectively divide the pool into two, one group playing the first half of the round and other playing the second half. Perhaps there the constraint could be set at 2, with a 1-match-length break between each Round. This would have to be somewhat adjusted for regionals with numbers not exactly divisible by 6. Get working, FIRST contractors! |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| "Live with Lucas" Mock Match | Tomasz Bania | General Forum | 14 | 10-04-2006 09:50 |
| "Random" Match List Generation | Sean Schuff | Regional Competitions | 32 | 01-04-2006 21:26 |
| New NEMO White Papers! "Creating a Killer Packet" and "25 Ways to Sponsor" | Jessica Boucher | Team Organization | 0 | 10-08-2005 10:55 |
| "Thunderbirds" Vs. "Team America" Which one will rule the box office? | Elgin Clock | Chit-Chat | 3 | 07-09-2004 19:53 |
| "Random" pairings | Ken Delaney | General Forum | 5 | 25-03-2002 00:38 |