MATLAB Programming Contest Blog

November 15th, 2010

Limbo! The 100 Node Challenge

The surprises keep on coming. I was impressed with the improvements made through Sunday, particularly noting Sergey’s big improvement with StarCat1. As I said, it’s hard to make big gains by the time Sunday rolls around, and Sergey showed us a 3.71% improvement. So I was shocked to see Peter van der Walle take the lead this morning with an incredible 4.42% improvement on his nickelfelpeter. Not only that, the size of the code started to nosedive at that point, leading us to some fierce, lean code.

We often do a 1000 node challenge right about now in the contest, but since the leading entries are already at about 1000, we really wanted to set the limbo bar low. The new challenge is to see what you can do when you’re limited to only 100 nodes. Yes, that’s a tiny number, but necessity is the mother of invention. Whoever can achieve the best score by midnight on Tuesday, UTC (7 PM in the eastern US) will win the 100 Node Challenge. The top of the Statistics page has a section dedicated to showing who’s in the lead while satisfying the required 100 node limitation.

3 Responses to “Limbo! The 100 Node Challenge”

  1. the cyclist replied on :

    Will you be displaying the number of nodes in each entry, as an aid to the 100 Node Challenge?

  2. Alan Chalker replied on :

    A clarification please: is it < 100 nodes or <= 100 nodes?

  3. Ned replied on :

    The “length” numbers are now appearing on the statistics page, and the rule is < = 100 nodes.

Leave a Reply

Wrap code fragments inside <pre> tags, like this:

<pre class="code">
a = magic(3);
sum(a)
</pre>

If you have a "<" character in your code, either follow it with a space or replace it with "&lt;" (including the semicolon).


MathWorks
The MATLAB Programming Contest is a semi-annual competition where contestants submit MATLAB code to try to solve a challenge.

See behind the scenes of the MATLAB Programming Contest

These postings are the author's and don't necessarily represent the opinions of The MathWorks.