Important: Participation Rules. The rules are updated. Links to past puzzles and result reports can be found at the end of that entry.
Difficulty of this round: middle++
Submission deadline: August 16th, 2008 (since there hasn’t been any submission for this puzzle till August 16th, the deadline is now October 16th, 2008. The T-shirts as prizes will have the new Drools logo printed on them. Added on October 15th: there still isn’t any submission yet…is this puzzle really that difficult? The new deadline is now December 16th. )
Submission email: droolspuzzle@gmail.com
This time we’d like to see implementation of the codebreaker for a variation of the classic game “Mastermind“.
Please refer to the wikipedia Mastermind page for the game’s basic rules. Our variation employs 12 different colors and 8 code slots. The CodeMaker.java is provided here. Participators must use this class as codemaker. The inline documentation of this class explains the judging rules in detail. The main method in the CodeMaker.java demonstrates how to call the code getter and how to use the answer judge.
Participators are required to write the codebreaker part of the mastermind application. Maximal trials is not specified in our codemaker, your should design a strategy which can minimize the number of trials.
Your test code should break 1000 different codes and output
- the number of average trials for breaking a code,
- the average time used for breaking a code
Something looks like this:
long totalTrials = 0;
long startTime = System.currentTimeMillis();
for (int i = 0; i < 1000, i++){
CodeMaker maker = new CodeMaker();
CodePeg[] code = maker.getCode();
// call your code breaker routine here
//...
}
long endTime = System.currentTimeMillis();
System.out.println("Average trials per code-breaking: " + totalTrials/1000);
System.out.println("Average time per code-breaking: " + (endTime - startTime) / 1000 + " ms");
Your code should be reasonably packaged and documented. Please by all means document your strategy as comprehensible as necessary.
