Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Fall 2008 MATLAB Contest, November 5th-12th
Date: Thu, 6 Nov 2008 22:04:02 +0000 (UTC)
Organization: Harvard Medical School
Lines: 8
Message-ID: <gevpki$bt2$1@fred.mathworks.com>
References: <ger09l$7v0$1@fred.mathworks.com> <gesrql$476$1@fred.mathworks.com> <bb078bed-9695-4efd-a866-e5e5a652cf42@r15g2000prh.googlegroups.com> <gevfju$q8d$1@fred.mathworks.com>
Reply-To: <HIDDEN>
NNTP-Posting-Host: webapp-05-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1226009042 12194 172.30.248.35 (6 Nov 2008 22:04:02 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Thu, 6 Nov 2008 22:04:02 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 51934
Xref: news.mathworks.com comp.soft-sys.matlab:499394


I agree. It will be MAJOR problem. I can see situation when best result for the day (next King of the Hill) will not be determined until the end of the next day. And this is even without intentional stalling the queue. One option is to cut number of steps to 200-500. Additional benefit of shorter run is preventing &#8220;kill everybody then collect&#8221; strategy.

"Alan Chalker" <alancNOSPAM@osc.edu> wrote in message <gevfju$q8d$1@fred.mathworks.com>...
> Looking at the entries that have run so far, it appears time is going to be a MAJOR problem this time around.  The 'contest' machinery itself appears to take over 70 seconds just to run the default 'simple' job.  This is nearly half of the max allowed time of 180 seconds.  I don't recall ever having a situation like this in the past.  
> 
> Because we have no control over the number of time intervals that get run or the number of boards, we'll never be able to get below that 70 second time frame.  In fact, the situation is about to get worse, because once the house solver gets replaced by an user submitted code, it's going to add significantly to that overhead, perhaps as much as doubling it.  
> 
> In developing my solver, I noticed that on some of the simple boards I was able to kill all the opposing ants and transfer all the sugar to the base in a very small amount of time (~200 time intervals).  The remaining 800 intervals were just 'wasted time' at that point.  Perhaps a change could be made to the run contest code that stops a board if all the ants are dead and all the sugar is at the base?  Alternatively, maybe our solvers can provide an output that means stop running this board and score it as is?  Either of these solutions would potentially allow us more control over the time it takes to run.