3 Commits

Author SHA1 Message Date
dave
dcefe6cdad Replaced the timeslot scheduler. This one is much faster, but it doens't actually compute cost for the number of judges the student has in a row. But, because it's totally random in layout multiple judges in a row should happen very infrequently. 2006-08-08 06:51:07 +00:00
dave
03acd9d8fc Use the annealer to assign projects and judges to timeslots. This should
prevent a project from getting too many judges in a row, and also a judge from
judging 2 projects at the same time (which would be more of a problem).

Still need to write a verifier to check all the results.  But the annealer
tests look pretty good.  Unfortunately it takes a pretty long time to run. :(
2006-08-08 03:21:08 +00:00
dave
e7d726355d The new judge scheduler.
- Missing: Having a project judged more than once by different judging teams is
  untested, I don't htink it'll work properly, still working on that part.
- Missing: Auto updating the configuration if any of the variables are missing.
- Missing: A way to preserve judging questions (like willing_chair), so the
  user doesn't delete them and break the scheduler, OR, notice saying that the
  question has been deleted and the scheduler won't use the chair calculations,
  then we need a way to add them back in with the click of a button.
2006-08-01 19:43:15 +00:00