
January 27th, 2005, 03:03 AM
|
|
Registered User
|
|
Join Date: Apr 2007
Posts: 22,309
Time spent in forums: < 1 sec
Reputation Power: 25
|
|
|
RE: RE: Contest Reorganization
Quote:
Quote: | in the last contest, i would hypothesize that the 2nd type of judging script was created much later only by zack |
Your hypothesis is correct. |
Yes, this is the kind of judging script I was talking about. Bascially my advice is to have all of the contest infrastructure setup before the contest begins, so all that you need to do at the end is plugin the entries and testcases. This is more upfront work for the admins/judges, and it requires some dicipline on their part, but it doesn't really make for more work in total and should make for a smoother event.
Quote: like, each participant would be able (not obligated) to submit up to 10 test cases, and possible even a small text describing why he/she thinks his test cases are good.
then, when everyone submits, the judge(s) would decide what submited test cases (if any) to use from each contestant (or if he is not sattisfied with them, only then would he create his own).. |
I'm not sure this is a good idea. Why make things unnecessarily subjective? What advantage does it give you?
I guess it depends on the nature of the contest, but by limiting each entrant to a small number of test cases I think you'll have more interesting (and thus, I would say, higher quality) testcases. If you are going to filter the testcases that are submitted, I think there should be some objective metric: like you take the N cases with the greatest range between hi-score and lo-score, or you take the N with greatest statistical variance in score. You might also want to constrain things so that you don't accept more than M testcases from any one person. I agree that the judges should be able to add their own testcases to the mix, and that contestants should not be obligated to provide testcases.
Anyway, just my two cents.
|