Major improvements to the Adjudicator Allocation

[Klaas van Schelven]

Hi all,

First of all, I'm lifting the "danger on the trunk" sign. This should be a good moment to check out the latest developments, or start thinking about you own contributions again.

I've added quite a lot in terms of the Adjudicator Allocation algorithm:

Generally, I've taken Ciaran's comments to heart and moved focus to getting the right chairs in the right debates first, and other parameters later. Everything stays configurable of course.
This is reflected in the "ciaran_perfect_chair" parameter.... this parameter tries to optimize to get the best chairs in the best debates.

The algorithm now also considers moves from one panel to the other, as opposed to just swapping 2 people all the time. This means panel sizes may vary too (because many adjudicators are moved out or into one panel), which can be held in check again by two different parameters (one which tries to give the best debates the biggest panels, and one which just ensures there's never more than 2 sizes of panels (like panels are 3 or 4 adjudicators)).

Further changes:
* The energy calculation is also displayed after manual changes now; enabling users to see the effects of their manual changes (and see if they can do better than the algorithm). This should also help warn for manually introduced conflicts or other overseen side-effects.
* The adjudicator allocation details are displayed sorted and slightly more readable
* Possibility for refining Adjudicators incrementally added (i.e. you can ask the computer to run the algorithm again, based on the results of the previous time, or after you've manually helped it over a hump)
* Locking of the Automated Draw Algorithms - to prevent trouble when someone hits Reload too soon

I would really appreciate it if this stuff is picked up in a real tournament soon. I think it represents a huge leap forward in this whole adjudication allocation bussiness....
However, it's all very new and shiny, so I would very much recommend to spend at least half an hour playing around with it to make sure you're familiar with it, but also that I haven't created any new bugs.

Klaas