Spring 2010 MATLAB Contest, April 28 - May 5
in [Matlab]
|
Prev: Single number into vector elements
Next: neural network
From: the cyclist on 4 May 2010 11:03 "Helen Chen (gmail)" <hhchenma(a)gmail.com> wrote in message <hrpaf5$1nd$1(a)fred.mathworks.com>... > Dimitri had a suggestion about the contest in a different thread: > "It would be usefull for players to be able to cancel their submission while the last is yet in qeue, if they realise that this submission has bugs or errors. With this capability the qeue list would shrinked giving a breath to mathworks contest computer and reducing the mean waiting time till submission evaluation. I hope mathworks contest team take this as a usefull peace of advice. Please reply me wether or not you agree with me. " > > I'm interested in feedback from other players. Is this something that you would think would enhance your contest experience? > > Thanks for your feedback! > Helen I would personally almost never use such a utility. Unless lots of people are submitting buggy code at crunch times (doubtful), and they realize that between time of submission and time of processing (doubtful), it will have minimal impact on the contest.
From: Amitabh Verma on 4 May 2010 11:11 "Sergey Y." <ivssnn(a)yahoo.com> wrote in message <hrpc50$p6o$1(a)fred.mathworks.com>... > I do not expect anybody to use it in real life if it does not affect submission counter. > If you remove deleted submission from submission counter, then life will be even more hectic – possible rush of submission deleting when new leader appears. > > I am sorry for beating a dead horse, but I have only one dream – CAPTCHA. > Sergey Now that everyone has to login before submitting their code. Is it possible to only process 1 entry per user at a time so that others who are in queue do not have to wait. Of course CAPTCHA is there but will it still deter the determined ones. The 1 entry processing was one of suggestions from last year.
From: Sergey Y. on 4 May 2010 11:32 Yes, submission limit helps partially with queue lag. I am not saying I do not like it. My main problem is with automatic tweaking machines. If one wants to do tweaking then one has to do it manually. Sergey "Amitabh Verma" <amtukv(a)gmail.com> wrote in message <hrpde8$mvs$1(a)fred.mathworks.com>... > Now that everyone has to login before submitting their code. Is it possible to only process 1 entry per user at a time so that others who are in queue do not have to wait. Of course CAPTCHA is there but will it still deter the determined ones. The 1 entry processing was one of suggestions from last year.
From: Alan Chalker on 4 May 2010 11:45 "Helen Chen (gmail)" <hhchenma(a)gmail.com> wrote in message <hrpaf5$1nd$1(a)fred.mathworks.com>... > Dimitri had a suggestion about the contest in a different thread: > "It would be usefull for players to be able to cancel their submission while the last is yet in qeue, if they realise that this submission has bugs or errors. With this capability the qeue list would shrinked giving a breath to mathworks contest computer and reducing the mean waiting time till submission evaluation. I hope mathworks contest team take this as a usefull peace of advice. Please reply me wether or not you agree with me. " > > I'm interested in feedback from other players. Is this something that you would think would enhance your contest experience? > > Thanks for your feedback! > Helen Yes, I can think of several situations where this would be nice to have. I've several times submitted some code only to realize I made some sort of infinite loop mistake. Instead of waiting for the 3 min limit to time the code out (and backing up the queue) it'd be nice to be able to dequeue it.
From: Alan Chalker on 4 May 2010 11:55
"Sergey Y." <ivssnn(a)yahoo.com> wrote in message <hrpelk$f8o$1(a)fred.mathworks.com>... > Yes, submission limit helps partially with queue lag. I am not saying I do not like it. My main problem is with automatic tweaking machines. If one wants to do tweaking then one has to do it manually. > Sergey > I'd like to point out that the contest has 3 distinct phases for a reason. Darkness and twilight mostly prevent tweaking and are almost always won by those contestants with an expert level understanding of the underlying algorithms. Many of those contestants deliberately don't participate during the daylight phase because of the nature of the contest completely shifts to tweaking and optimizing. With the 10 entries / 10 mins limit now, there is no speed advantage of manual tweaking over auto tweaking - it's just a time commitment issue. If we are going to suggest arbitrary rules, I have a major issue with non-descriptive variable names and poorly documented code and think all leading entries need to be screened for that. But most competitors don't want to do that because again it's a time commitment issue. One of the things I personally enjoy about the contest is developing code the deals with the contest mechanics (i.e. the auto submission code). I found it particularly challenging to create new code to handle the new site. In fact I spent most of the weekend doing that (which is unfortunately why I didn't get a chance to submit a documented leading solver like I usually do). |