Implement better (customizable?) selection strategies about gavel HOT 4 CLOSED

Also, it would be cool to have location-based judge dispatch (it's nice to not make judges walk all over the place).

from gavel.

@zacharyliu, based on his experiences at HackPrinceton, said that some issues they had were:

• some judges might’ve gotten sent to the same project at the same time (heard reports of double judges)
• order of projects not optimized to reduce walking distance (we had two floors, and judges complained of constantly going up/down stairs)"

from gavel.

d537db4 improves judge selection by making it so each project is seen some minimum number of times before selecting projects to maximize expected information gain.

There are a couple things that still need to be considered / changed:

• Do we take into account people who are assigned to a project (but haven't finished judging it) when counting number of times a project has been seen?
• How can we make it so two judges are never at the same project (when possible)? We could just ignore all items that are some Judge's annotator.next, but what if a judge never shows up? The team will be stuck without a judge. We could fix it with some kind of timeout or something…

from gavel.

Okay, I think this is a pretty good solution: b3317da.

from gavel.