From: the cyclist on
"Helen Chen" <helen.chen(a)mathworks.com> wrote in message
<fv82i0$nql$1(a)fred.mathworks.com>...
> Just a reminder to let everyone know that the Spring Contest
> launches tomorrow, Wednesday May 30th at high noon. Be
> there or be square!
>
> See you then!
> Helen

Thanks for running another fun contest. Not actually having
access to MATLAB anymore took some fun out of it. 8-/
Didn't stop me from tweaking here and there, though.

From: Yi Cao on
How about using an anti-spam tech, such the one used for
File Exchange review comments to prevent automatic
submissions, i.e. a user has to copy certain characters
shown on the screen before he/she can submit a code. This
has been used in File Exchange, hence should not be
difficult for TMW to implement in the contest page.

Yi
From: David on
"the cyclist" <thecyclist(a)letter.after.f.mail.com> wrote in
message <fvsk1d$m84$1(a)fred.mathworks.com>...
> "Helen Chen" <helen.chen(a)mathworks.com> wrote in message
> <fv82i0$nql$1(a)fred.mathworks.com>...
> > Just a reminder to let everyone know that the Spring Contest
> > launches tomorrow, Wednesday May 30th at high noon. Be
> > there or be square!
> >
> > See you then!
> > Helen
>
> Thanks for running another fun contest. Not actually having
> access to MATLAB anymore took some fun out of it. 8-/
> Didn't stop me from tweaking here and there, though.

Congratulations to Tim for winning the 1000 node prize, ...
without actually having access to MATLAB !

-- David Jones


From: Yi Cao on
I strongly agree that using random function will discourage
algorithmic development because a well-tuned random code
will significantly disadvantage any new algorithm, which
has not been tuned for the specific test suite.

As Markus said, using random functions here is total
different from the use in a GA type algorithm, where the
statistical nature of a random function is used to get the
optimal solution.

However, here, the random function is used just like other
parameters to be tuned specificly for the test suite. By
doing so, when altering an algorithm, the number of random
function calls will change as well, hence the result is
completely unpredictable.

The main problem with random function is that it
has 'memory', so that previours use of a random function
will affect the follows. As Nathan mentioned, disallowing
random function will not solve the problem because a user
can develop his own.

However, I would like to suggest to use a random function
in runcontest function to make tuning random parameters
imposible. For example, in runcontest function, a line of
rand('state',sum(100*clock)) can make any intention to tune
a random parameter impossible because even with the same
parameters, the results could be totally different if a
random function is used in a code.

Yi
From: Steve Hoelzer on
"Yi Cao" <y.cao(a)cranfield.ac.uk> wrote in message
<fvsl6t$5db$1(a)fred.mathworks.com>...
> How about using an anti-spam tech, such the one used for
> File Exchange review comments to prevent automatic
> submissions, i.e. a user has to copy certain characters
> shown on the screen before he/she can submit a code. This
> has been used in File Exchange, hence should not be
> difficult for TMW to implement in the contest page.
>
> Yi

Excellent idea! It wouldn't eliminate tweak bombing, but at
least it would make it harder.