Commit Graph

7 Commits

Author SHA1 Message Date
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
james
c5e55fad37 Remove the unneeded configuration params for timeslots from the scheduler
Separate the 'requirement check' into a separate file and run it on both the config  page, and as a double check on the actual annealer page incase they decide to manually type in the address or bookmark or somkething.
2006-01-31 22:34:04 +00:00
james
eaa1444082 Make the scheduler config check for available timeslots
Make the scheduler actually insert the timeslot/project/team data into the database
2006-01-26 23:06:47 +00:00
james
b4fc47f9b7 Add a huge warning about the scheduler not yet being complete. 2006-01-16 05:04:45 +00:00
james
635d0b6e2d Fix annealer to only use judges that are complete and from the current FAIRYEAR 2006-01-03 02:44:26 +00:00
james
c53e130cc4 Fix the scheduler config to work with multi-year data 2006-01-03 02:33:11 +00:00
james
44a79493aa Get age category preference from judges as they register
Create scheduler configuration page to handle setup parameters for the automatic judge team assignments
Create the annealer to handle the actual assignments of judges to judging teams based on the lowest cost function of each individual team.  Currently takes into account: a) age category preference, b) divisional areas of expertise.  still requires: years of experience, language preference, and 'team captain' scheduling.
2006-01-03 02:08:23 +00:00