|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Real Week 2 update
Quote:
|
|
#2
|
||||
|
||||
|
Re: Real Week 2 update
Quote:
With respect you are way out in left field on this topic. Last edited by wireties : 15-03-2016 at 02:30. |
|
#3
|
|||
|
|||
|
Re: Real Week 2 update
Quote:
Last edited by Boltman : 15-03-2016 at 08:41. |
|
#4
|
||||
|
||||
|
Re: Real Week 2 update
I would like to note that with small sample sizes it is statistically likely to see patterns that aren't actually there.
|
|
#5
|
|||
|
|||
|
Re: Real Week 2 update
Quote:
It did not affect us one bit. Neither did losing 2 RP in San Diego. We were good enough to get what we deserved either way. Last edited by Boltman : 15-03-2016 at 09:00. |
|
#6
|
|||
|
|||
|
Re: Real Week 2 update
Quote:
NoCal. Good luck 254 your bot rocks. |
|
#7
|
||||
|
||||
|
Re: Real Week 2 update
There is no "perhaps" here. The algorithm does not factor in team numbers or team history. Rather than pontificate here, consider talking with an FTA or reading up on the matchmaking algorithm to understand how it works.
http://www.idleloop.com/matchmaker/ |
|
#8
|
|||
|
|||
|
Re: Real Week 2 update
Quote:
"it's desirable to minimize duplicates so that teams see as many different teams as possible. It's especially desirable for a given team not to have the same team as a partner more than once, nor as an opponent more than once." I think they could have split 1678's second match against us to another match just sayin'. Its not really ideal for any team to face consensus #1 twice in qualifications or 20% of their matches. I'm sure the algorithm tries to be unbiased however as we know it can be imperfect (as the above link states) a human FTA should look for duplicates and adjust as necessary. Just flip teams above or below any "peculiarity" a one game switch in the schedule is doable. I am not pontificating (you chose to read a post in my week 2 update thread), just pointing out the realities of a single regional's scheduling that happened to have 4 World Champions everyone in FRC knows. Also I disagree with this statement "This is not only a scheduling algorithm issue, but a simple matter of not knowing in advance which teams will turn out to be more effective than others." I believe "Class" has a lot to do with year to year success in a 20 year organization of 4000 or so teams... just like in horse racing. So to say that 254 or 1678 or 973 or 1323 are all the sudden not going to be good is a false statement. they will likely be very good because of their programs and their history. They would not accept anything less. Same here we are not going to fall off the face of FRC either every year we will iterate better. You can assume certain things from how teams have done in the past. Just look at their year over year results its all there. I think to really do scheduling "correctly" some unbiased FTA needs to "adjust" when the computer prints out what it thinks is optimal based on some algorithm. The FTA knows or should know the perennial teams and could easily see the duplicates or inordinate amount of powerhouse pairings with a single highlighter . They could adjust anytime up to when its posted. It can be done and I think it improves the game play as well if instituted correctly. The main problem is.. teams only get maybe 20 matches in two regionals so scheduling draw is huge just like "missed RP's" as a high order ranking metric. I'm not afraid to point things out to improve the game hopefully for every team. FRC is great yet can still improve and tweak. Its good to be questioned and not accept always the status quo. I may just have a fresh view on an older institution. Things can always improve. This is not why we are not in St Louis. All I'm sayin' it could be done better...and perhaps it makes a smidgen of difference if they actually tweak the way schedules are made. Might take a half hour or less at each regional to flip a few teams a few spots with the analytic help. ----------------------------------------------- Attached is the way I do schedules lets pretend its a different season and in this scenario 3495 is a super powerhouse and consensus #1 or won 4 WC divisions and its our second match with them on our side. Great for us but seemingly "unfair" for having #1 twice on our side (or against us) I mark partners in green and opponents in red for my scouts. Whites we do not play. So if an FTA wanted to by switching 5137 for 2135 a one game switch a second powerhouse pairing match is avoided then all they have to do is make sure the other 5 teams did not play that team on same side or not. There are plenty of white spaces to switch teams around IF the goal is to be more random and possibly more fair to all teams. If that does not work then there are two other "blue" teams that could make the switch. We could have probably used the extra game in between as well there...in that scenario. Just like with instant replay, changes can be made that are fairly simple and don't open a can of worms.... what might actually happen is all the sudden more teams get super good alliance partners and avoid facing powerhouses too much until eliminations. Schedules are always pretty late anyhow. I think a human eye on it could easily sort out inconsistencies, much easier than trying to program some algorithm..its not rocket science. Let the algorithm do the sort.. then highlight several inconsistencies and move things around slightly. Last edited by Boltman : 15-03-2016 at 13:27. |
|
#9
|
||||
|
||||
|
Re: Real Week 2 update
Quote:
Changing the algorithm to try and pair teams of different ages with each other was tried once, in 2007, with generally disastrous results. The match making generator is already far from random when you consider all of the constraints on it - adding more constraints to make schedules "fairer" all but requires loosening one of the other constraints. In 2007, this meant matches had a consistent mix of young teams, old teams, and middle aged teams... at the cost of having to play with and against the same robots over and over again. It was almost universally disliked. My advice? Get over the fact that schedules won't ever be "fair" however you see it, and work on becoming a team that isn't dependent on a perfect schedule to play well into Saturday / Sunday afternoon. |
|
#10
|
||||
|
||||
|
Re: Real Week 2 update
Quote:
I felt guilty ranking so high with such a poor performing robot. I refuse to even count it as our highest ranking ever at an event. |
|
#11
|
|||
|
|||
|
Re: Real Week 2 update
Quote:
I foresee maybe about three glaring inconsistencies that may need to be adjusted per "powerhouse" event... an hour of work maybe just making sure it does not mess another team up. The system is decent I believe it can be improved. Just like missed defense crossings that also can improve. Pretty sad when Portcullis crossings are missed especially the way we did them ![]() Last edited by Boltman : 15-03-2016 at 14:18. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|