People often live all over the place. One of my teams includes somebody from Oakville and someone from Pickering. Also, in many cases it's not their home address that's important to them but their work address, the address of the daycare, etc. Perhaps something to use as a first guess if we end up with an algorithm that's based on teams setting a single "ideal" location. Greg.
_____ From: [email protected] [mailto:[email protected]] On Behalf Of Todd McDonald Sent: Monday, December 14, 2009 7:17 PM To: Development discussion for the Leaguerunner league management system Subject: Re: [Leaguerunner] Changes to scheduling algorithm Evening, Sudbury is a much smaller club, so we only have one field to worry about. I was giving it some thought though, and for you bigger clubs, is it common for most teams to have home addresses that are close together? It could be possible to convert home addresses into geocode and build bounding polygons per team. Then it's just vector math to find the field closest to the middle of the two team polygons. The nice thing about it would be that it's completely behind the scenes, as it's all based on team addresses, which would take a lot of coordination on the part of a whole team to game it. Of course, if most teams don't follow that trend, it's completely useless. Just my $0.02 Todd McDonald On Fri, Dec 11, 2009 at 3:00 PM, Greg Schmidt <[email protected]> wrote: Anyone had recent thoughts on this stuff? My concern with the idea of giving each field a value is that we have a LOT of fields (30+? And yes, that's field sites, not individual pitches) and it seems like a bit of a UI nightmare, as well as unrealistic to expect a captain to wade through all of that. Captains are often a little overwhelmed already by everything they have to do, and adding in another page with a huge array of choices may be over-the-top. Greg. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave O'Neill Sent: Thursday, November 05, 2009 1:52 PM To: Development discussion for the Leaguerunner league management system Subject: Re: [Leaguerunner] Changes to scheduling algorithm On Thu, Nov 05, 2009 at 01:09:30AM -0500, Patrick Malka wrote: > I just thought of another option for field component. > > Users would give each field a numerical value 1-10 that would be used in the > calculations so that the teams could determine the relative ranking of the > fields instead of the default 1,2,3,4,5... The team could then have several > level 1 picks, and no level 2 picks and some level 3 picks and then all the > rest 10... Having them generate a total ordering of their choices is probably better from a UI perspective. Asking them to assign numeric values to intangible items like "how much do I really want to play here" is a pain -- similar to what we've seen in the past with SOTG ratings :) > I would have to look at that in more detail to come up with math that works, > but it should be possible. If anyone thinks it is worth doing, I'll take a > look. Yeah, I'd love to see a proof-of-concept for the algorithm in the previous post. For once you and I seem to actually agree about something :) Cheers, Dave _______________________________________________ Leaguerunner mailing list [email protected] http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner _______________________________________________ Leaguerunner mailing list [email protected] http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner
_______________________________________________ Leaguerunner mailing list [email protected] http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner
