Think you can elaborate on the time judging, like what's too long?
Think you can elaborate on the time judging, like what's too long?
The time will be judged compared to other entries. The fastest entry for a particular challenge will be awarded with a 10; the other entries will be awarded with a score proportional to the additional amount of time it takes.
For example, your entry takes 4 minutes to find a solution for a particular challenge, but the best entry only took 2 minutes. Your entry would be awarded with a 5 for that challenge.
I'm debating whether or not to weight the time that heavily. Opinions? How would you want your program judged?
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
I think the time and squares uncovered should be tied together, becaue 1 entry may find a simple solution in seconds where another may find a more complete solution but take 2 minutes. Timewise how do you judge one against the other?Originally Posted by pianorain
You might try doing a ratio squares/sec or something to that sort
Can we multithread?
I agree with Darryl. The game you gave a link to gave both the score and the number of boxes which were eaten. But I guess if you can eat all the boxes, the overall score becomes rather redundant doesn't it.
Also, I think there should possibly be some method of insuring that everyone's game area has the same number (roughly at least), of numbers ... I mean 18*18 sure, but the values of the cells is what I mean. If someone had a box full of 6's, they would be rather more likely to get a higher score than if they didn't. That is if the idea started by Darryl is implemented. But the tough choice is how to judge the score if both are to be taken into account.
Just by doing a quick test, it gives the score by: summing up the number of every box you eat, and multiplying the result by 10.
This is a great idea. I'll do that.
II. Revised Code Judging
II.I Submitted code will be judged based on the following:
Compiliation (0 - 10)
How easy it is to compile. Warnings detract from this score.
Success x 5 (0.0 - 10.0)
Each entry will be given five boards to solve. This will be graded depending upon how well and how fast the code performs the desired task compared to the other entries.
Coding Style(0 - 10)
Code efficiency, is the code readable? Are good programming practices followed? (Are processes closed when finished, do you use arrays when initializing multiple variables under one instance, and do you free memory after allocation?)
Best Code Score: 70.0Sure, but if you use any non-standard libraries, make sure to say that you do and include a location where I can get them.Everyone will get the same five challenge boards.
Last edited by pianorain; 05-19-2006 at 07:40 AM.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
Ok I am done with my entry, just optimizing now...performance wise it will uncover about 175 squares in under 2 sec, if allowed to keep running it reaches around 210 in about 15 seconds and then improvements after that are slow, but I am still tweking it. So depending on the timing judging, it may be better for me to end at 2 secs. instead of holding out for the 15 seconds.
Oh Dear, I haven't even started it yet ...
woohoo, I beat the high score on ebaums page, with 7250. unfortunately it doesn't save it to the page. Anyway I am done and will email it tomorrow after I add a few more comments and maybe rename a few variables.
Good luck to the rest of you :-)
I'll enter, since I started to write code. Not sure how much of a chance I stand, but we'll find out, I suppose.
Darryl's doing a good job of making the competition nervous. ;-)
long time; /* know C? */
Unprecedented performance: Nothing ever ran this slow before.
Any sufficiently advanced bug is indistinguishable from a feature.
Real Programmers confuse Halloween and Christmas, because dec 25 == oct 31.
The best way to accelerate an IBM is at 9.8 m/s/s.
recursion (re - cur' - zhun) n. 1. (see recursion)
>> Darryl's doing a good job of making the competition nervous. ;-)
I bet it's all just show, bet he doesn't have anything done in it!
>> The best way to accelerate an IBM is at 9.8 m/s/s.
haha
Sweet. I'm also writing some code, but I won't enter. That might be a bit of biased judging.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
it's submitted, which pianorain can verify>> Darryl's doing a good job of making the competition nervous. ;-)
I bet it's all just show, bet he doesn't have anything done in it!
>> The best way to accelerate an IBM is at 9.8 m/s/s.
haha
I'm in.
Just a reminder, you've got about two weeks to submit an entry for this contest. So far, the only entry I've got is Darryl's.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
