Nope. Done all the time. Otherwise you start to define ways to handle every possible case, most of which will never happen, and some that you failed to think of that will happen. How many events will you vacate? Will you vacate for all infractions or just certain ones. What if the protested program offers some explanations that have a bit of plausibility? What if he fails to respond at all? What if he even refuses to present the source? Etc. Too many cases to handle, the current rule is clear about what is allowed in an entry (original code, or author names if others provided some of the code) and what is required (source if demanded.) For every ACM event I want to, I had a copy of my source. In the early days, this was a printout. One of those was what I sent Carey years ago to try to resurrect a working copy of Cray Blitz from such a printout. In later days, it was source files on a laptop.Dann Corbit wrote:Doesn't that strike you are rather arbitary?bob wrote:I think that was one of the things we chose to leave until the circumstance arose, rather than have long debates, and try to cover every conceivable case. It is easier to let it happen, then you have context for making the decision...Dann Corbit wrote:Upon examination of the rules, including this one:bob wrote:I believe the entry forms are kept on the ICGA web site. I do not know if all versions are present, or just the one for the most recent WCCC event. But they have all been pretty clear about the requirement for source code should a protest be filed.Dann Corbit wrote:Do you know where I can find a copy of this agreement?bob wrote:The problem is, when you apply to play in an ICGA event, you are required to sign an entry form that includes specific requirements a program must meet, and requirements an author must meet should a protest be filed.Dann Corbit wrote:Yes, those are good points and especially in the case of Pete Rose, the outcome clearly has the force of law because his reputation is utterly ruined and his livelihood is destroyed.bob wrote:NASCAR has a set of rules. After the race, the winner's car is impounded and gone over with a microscope. If a violation is found, it is disqualified. In track and field events, if a drug test is failed, titles are vacated, participants can be banned for a period of time including life. This is common in any sort of organization that handles contests. Pete Rose comes to mind in baseball. A manager that bets on baseball games. Baseball has a rule that managers and players can not bet because they have the ability to alter the result of a game by how they play or how they manage, which is a big conflict of interest. Pete Rose violated that rule. Where is he today? outside looking in, yet he was one of the best ball players of all time. And won't be allowed in the hall of fame because he violated a simple rule. And he didn't even bet on his own team or games his team played in. But the rule was a rule.
Every decision made on the planet does not go through the courts. Nothing would get done if that were required.
I still don't like the process chosen by the ICGA. I do not know enough about baseball bylaws and processes to know if I do not like the handling of the Pete Rose process.
I would like to read it, in particular for each of the years that Vas competed in the competition.
I am particularly interested in the exact wording of the agreement and the exact wording of the penalties.
It is quite possible that the ICGA acted properly if Vas has violated his agreements and if the ICGA acted as they spelled out in their contracts.
Here is rule 2 which is where the current issue lies:I have never seen a formal statement about potential penalties for failing to follow rules. In general, you get kicked out of any tournament where that happens. This is a first, so far as I know, for a case that spanned several years.2. Each program must be the original work of the entering developers. Programming teams whose code is derived from or including game-playing code written by others must name all other authors, or the source of such code, in their submission details. Programs which are discovered to be close derivatives of others (e.g., by playing nearly all moves the same), may be declared invalid by the Tournament Director after seeking expert advice. For this purpose a listing of all game-related code running on the system must be available on demand to the Tournament Director.
"2. Each program must be the original work of the entering developers. Programming teams whose code is derived from or including game-playing code written by others must name all other authors, or the source of such code, in their submission details. Programs which are discovered to be close derivatives of others (e.g., by playing nearly all moves the same), may be declared invalid by the Tournament Director after seeking expert advice. For this purpose a listing of all game-related code running on the system must be available on demand to the Tournament Director."
It was not at all clear to me that the rule includes inspection long after the tournament is completed (indeed, such a rule makes little sense in that context).
I think that the rule should be amended to make this clear.
On the other hand, it also does not say that the tournament director cannot demand the source code years later. So, in some sense Vas seems to have "sworn to what was bad for himself" by agreeing to a highly ambiguous document.
In my opinion he should have furnished the source code when demanded.
In going over the documents I found, I was unable to find any specific penalties, for example at this location:
http://www.grappa.univ-lille3.fr/icga/e ... .php?id=12
I complied with the rules as I understood them, and never had any problem except for the one protest that was investigated as carefully as the current case.