r/icfpcontest • • Aug 02 '14

Team Trup 16 submission and brief description

2 Upvotes

Here is the submission, pretty much has all we did:

  • Compilers for both machines for essentially the same c/python-like language (compiler.py and gompiler.py) with inline ASM support.

  • Emulators/debuggers for both machines (gcc_eval.py and ghc_eval.py)

  • Partial game emulator (ghosts are not moving)

  • A basic Dijkstra player - tries to detect dangerous moves and find the closest pill. Includes basic list/2d list set/get functions. (Identified to be retarded later on)

  • Ghosts: manhattan distance reduction + stuck detection (multiple deadends+same junction more than 3 times over) + stuck recovery ("hand on wall")+time waster.

Our team had two active members this year, who spent most of the time being scared of writing a compiler. Right after the deadline we realized how easy it was to make trees, proper (worst-case) forecasting etc. Looking forwards to our usual 64th place.

Team Trup 16


r/icfpcontest • • Sep 18 '09

ICFP Contest 2009 presentation [video]

Thumbnail
vimeo.com
3 Upvotes

r/icfpcontest • • Aug 28 '17

First round of the full contest results (2017)

Thumbnail icfpcontest2017.github.io
4 Upvotes

r/icfpcontest • • Aug 26 '18

Ways to make programming fun between ICFPCs?

5 Upvotes

ICFP contest is nice and challenging, it brings fun and gaming into programming... and then it's over. How do you make programming fun, while there's no ICFPC?

The most ICFPC-like game I've found so far:

What games would you recommend?


r/icfpcontest • • Jun 30 '09

Fatvat's Writeup (2009) [1/3]

Thumbnail fatvat.co.uk
6 Upvotes

r/icfpcontest • • May 19 '15

Contest page updated!

Thumbnail
icfpcontest.org
7 Upvotes

r/icfpcontest • • Aug 10 '15

Contest Review

7 Upvotes

My team "Over-long Viral Marketing Blurb"* has been doing the contest annually since 2007.

Here's my review of the contest for the organizers, while it's fresh in my mind.

Pros:

  • Flavor! The story for this contest was awesome, and the organizers staying in-character was great.

  • Problem was interesting! There will be more about this in our write-up later.

  • Logistics handled by the organizers! It's nice that we were able to submit a Windows build without the organizers throwing up their hands in confusion. We're game developers and we are quite spoiled by our development environment and tools.

  • Leaderboard game was fun, even if it doesn't have much impact on the final results. For us, the highlight of this kind of gameplay was the Cars and Fuels contest, but this one came close and we enjoyed the rivalries with the other teams on the leaderboard!

Cons

  • Problem was underspecified. Should we even bother handling low memory or low times? How much should the limitations affect our search strategy? Do we just give up if the maps are too big? Based on the scoring rules, big maps are going to be dominated by good power word pathfinding, small maps by good line hunting. What should we optimize for when deciding what to work on? We just have to guess and hope we pick a good lottery ticket.

  • No twist. Our Sunday submission is not much better (and in some ways worse) than what we had on Saturday. Many of the previous contests threw in a little twist late in the contest--for example, the Beards in the lambda lifter puzzle. Implementing this would have at least let us feel like we'd made some progress.

  • We miss the archaeological problems of 2006/2007. The pre-contest materials got us really excited that there might be a return to that style of contest, which hasn't happened in a long time. That said, we're fully aware how much more work those are to make!

Thanks for the entertaining contest! We are looking forward to seeing how the final standings turn out and reading the organizer's and other team's write-ups!

* This year our blurb was for Temple Gates Games which won awards in the Oculus game jam. Check out their game


r/icfpcontest • • Jul 20 '20

ICFPC 2020 writeup (warning, long rant)

16 Upvotes

This contest had a lot of great ideas and the organizers made a huge amount of really engaging content for it. Unfortunately, it was poorly executed and this was my least favorite contest of the 16 or 17 I've participated in.

The contest roughly divided into four phases:

  1. First 4.5 hours: more teaser material was released

  2. Next 20 hours: "galaxy" was released, and teams score points by completing the tutorial levels. Only four teams passed the first level of the tutorial (which involved waiting until two ships meet and then clicking a button), and only two teams passed the second level. Points earned in this round are only for the lightning round and do not contribute to final standings.

  3. Next 19.5 hours: 45 minutes after the lightning round was over, the organizers reveal that the main contest will be a tournament held between contestant's submissions. Details remain hazy except the occasional teaser picture continued to be tweeted out.

  4. Final 28 hours: organizers release an outline for the protocol for participating in the contest. Because of the scoring rules, that's less than 10 hours between between revealing how to participate and when points begin to accumulate.

The problem I had with the contest is that the different stages were mostly independent of each other. There was no way to hasten stage 1: the discord chat collectively blew through the teaser material in about an hour of work and 3.5 hours of waiting for the organizers to keep up with chat. With the release of the "galaxy" code, teams started working on writing interpreters to execute it, and only four teams got far enough to even score any points in the lightning round.

But the only value of working on stages 2 and 3 was to get a head start on stage 4 if you managed to finish the earlier stages in time. As for me, it was around T+50 hours I had a working interpreter (including gui and communicating with server, both of which are non-optional). Then when I started work on the contest itself, I threw out everything I had done and started from scratch. I would have actually done better in the contest if I had joined at the beginning of stage 4 and not wasted the first six hours of stage 4 completing my interpreter.

After finishing the interpreter, I beat the first 10 or so tutorial levels so that I had some idea what the contest was about and worked on making a dummy submission. By the time I had gotten a minimal valid submission, there were 13 hours left in the contest (including a minimum of 5 hours of sleep). Since I still have little idea of what the combat mechanics were, or even what many of the mysterious aspects of the server protocol did, it would be a waste of time to try to come up with any kind of a strategy. At that point I quit work, which was the first time I enjoyed this year's contest.

My noop submission made it to place 66 in the ranking, although by the time of the leaderboard freeze I had fallen to 79. The only way it can ever win a combat is if the opponent falls into the sun faster than it does, which presumably only happens against the other noop submissions, of which I surmise there must have been a lot.

The easiest thing to improve for this contest would have been making it plainly clear before the contest started that there was a minimum effective team size (probably 3, realistically). I would have preferred working with 2 strangers if it meant actually getting to see the content as it was meant to be seen. I bet this contest was a lot of fun for large teams that were able to make timely progress, and there was a lot of content to explore and discover for such teams.

Alternatively, just ditching stages 1 - 3 would have been a massive improvement. I still don't know why "galaxy" was delayed by 4.5 hours -- I don't think the organizers were just stalling for time because they weren't ready.

Overall, my main issue was lack of communication from the organizers. A lot of that was deliberate -- having to reverse engineer the combat mechanics was a poor decision, but not a big deal. Reverse engineering the communication protocol was just a waste of our time. Spreading relevant information out across 3 or 4 websites (which initially didn't even link to each other!) was aggravating. They had a mailing list, but never sent any emails to it. It would have been nice if they had identified themselves in discord chat from the beginning as organizers, and made it clear from the start that they would only be providing technical support instead of keeping up the faux "we're astronomers getting messages from aliens" facade. The tenor of the contest was set from hour 0 when, instead of releasing a contest spec like in most years, they released a blog post which linked to another blog post which linked to a partially completed documentation page.

I just don't get why the organizers didn't release a spec. Were they worried that the combat game wasn't interesting enough to withstand 72 hours of teams strategizing it?

The main thing I liked about this contest was that they made the submission system testable before the contest started. The submission system was solid (really, the whole contest seemed mostly technically sound) and I hope future organizers are similarly responsive about submission validation.

I think if you just forget the competitive aspects and make a personal goal of exploring the "galaxy" object, that would be a pretty feasible and fun task for a solo team taking around 48-72 hours.

Cheers to solo team Crashing Drives for helping me out in the discord chat.


r/icfpcontest • • Mar 26 '25

FYI: ICFPC 2025 Dates Have Been Announced (05-08 Sep)

Thumbnail icfpcontest2025.github.io
15 Upvotes

r/icfpcontest • • Jul 24 '26

Reminder: The ICFP 2026 starts in < 3 hours if you're interested and are unaware/forgot.

Thumbnail icfpcontest2026.com
6 Upvotes

r/icfpcontest • • Jul 23 '20

Frictionless Bananas 2020 ICFP Programming Contest writeup

Thumbnail sawicki.us
10 Upvotes

r/icfpcontest • • Jul 17 '20

ICFPC 2020 has started

Thumbnail
icfpcontest2020.github.io
6 Upvotes

r/icfpcontest • • Jul 30 '20

Team Rotten Lambdas ICFP Contest 2020 Retrospective

9 Upvotes

We are a team of three, living in Hannover and Vienna. We prefer to meet in person for the contest and settled for Hannover this year. We had created a GitHub repo in advance. The contest started on Friday at 15:00 local time, so we met for lunch, then set up our computers, opened the contest website, and started hitting the reload buttons on our browsers. The plan was to have a quick look at the task description, and unless it suggested the necessity of a 24-hour coding spree to compete in lightning, print it out and head to the next cafe or ice cream parlor to discuss the task and plan a strategy.

What we got was this:

"Dear participants of the ICFP Contest 2020. We have prepared a great contest for you! But we have strong reasons to throw it out and ask you to put your efforts into something else. ..."

At this point, we made a grave mistake that led to us eventually quitting the contest: we refused to believe them.

All the contestants were supposed to collaborate in decoding messages from space. Huh!? Collaborate? Wasn't this supposed to be a contest where teams are not allowed to exchange information? And where is the task description? This was so far from our expectations that we just failed to grasp it was real.

Instead, we thought it was an elaborate joke on the organizer's part, and we were sure that a real task description would appear in a few minutes. When this did not happen, we half-heartedly started to take part in the discourse decoding chat(*), but it quickly became apparent that the organizers or the infrastructure just could not keep up with the contestants - updates failed to appear even for messages that had long been decoded. At 16:25 the organizers announced that we should get ready for a really huge message. "Finally, the task description!" we thought. And waited... At 19:30, we got the huge message. But no task description.

Even we now realized that we should better start implementing something to have a remote chance for a lightning round submission. But what? The submission system had been published before the contest, so we knew we were supposed to submit one program. Since the messages defined an executable language, the only obvious thing to do was implement an evaluator. The representation of lists and booleans as functions seemed to require lazy evaluation, so I dug out a combinator graph reducer I had written years before (https://github.com/bokesan/skred) and added a simple parser for the message format. We had a working evaluator sometime after midnight. We didn't know what to do with it, though. We just picked vectors to send as input at by feel, and whenever the output looked interesting (meaning long - we looked at the text only) we kept that vector and added another one. We even got to the first SEND instruction that way.

We were so bent on doing something automatically that it took some time before we had the idea to actually look at these image things the evaluator produced(**). So one of use wrote a visualizer in Python. We never considered writing an interactive galaxy explorer, even after the organizers wrote that that was what we were supposed to do. We were like "Clicking in an image? In a programming contest? Might be a last resort attempt if you have no better idea, but not for us." Obviously, in retrospect, we were in complete denial about the task.

By this time, the lightning round was over, what to submit was still unclear to us, and we were angry and tired. So we went out to get something to eat and see if a pause and some chat-free time would get is back into course somehow. But it became clear that this contest was not for us, so we decided to quit. Not because we saw no way toward a solution and scoring - we have previously participated without any chance to finish in the top 20 or so, for fun. We quit because we saw no way to have fun during the rest of the contest.

--

On Sunday morning, I had nothing better to do and thought about how to solve this without the stupid (yup, still in denial) clicking approach. Why not have the computer click all locations within the image bounds? (Incredibly silly now that I know what the galaxy simulator contains, but it seemed like a good idea at the time). I implemented that, and my program got to the first SEND instruction in less than a minute. That made me so optimistic that I wanted to submit something just to get my cool auto-solver (I thought) in there. So I implemented a bot for the space battles. I started from fresh using Haskell - my aim was not to implement a good strategy, but just a correct implementation of the protocol, without timeouts or other errors. This took surprisingly long because I had misread the protocol at some places and also forgotten that the proxy used modulated messages, but I managed to produce a working submission. By that time it had also become clear to me that my auto-solving approach did not work - it had produced nothing more interesting after running for more than 24 hours, and only gotten to 21 clicks.

With a different mindset, this might have been one of the better contests - the last three years had seemed repetitive in parts. This was clearly different. Too different for us, apparently. Our preferred "printed task description in ice cream parlor" approach was not really suited for this year's contest :-)

Our "submission" is here: https://github.com/bokesan/icfpc2020

--

(*) I don't like chats and did not even register for discourse. Another team member volunteered for that. Chat and email is what's keeping me from coding

(**) That happened to me in 2007, too. I dutifully executed the DNA to generate an image file. But I never got the idea that intermediate images might contain interesting information.


r/icfpcontest • • Jul 27 '20

ICFPC 2020 submission by WILD BASHKORT MAGES

Thumbnail
github.com
8 Upvotes

r/icfpcontest • • Jul 22 '20

ICFPC-2020 writeup from team Just No Pathfinding (long rant, so just linking)

Thumbnail dastapov.dreamwidth.org
10 Upvotes

r/icfpcontest • • Jul 24 '20

ICFPC-2020, team Just No Pathfinding, part 3 (final)

Thumbnail
dastapov.dreamwidth.org
12 Upvotes

r/icfpcontest • • Jul 20 '20

ICFPC 2020 completed! Share your thoughts / writeups / strategies

7 Upvotes

Please share your thoughts / post-mortems etc.! If you've posted elsewhere, just drop a link below.


r/icfpcontest • • Jul 25 '20

Write-Up On ICFPC-2020 By A Casual Participant

Thumbnail
rmathew.com
6 Upvotes

r/icfpcontest • • Jul 03 '20

ICFPC2020 submission system requires git and docker

Thumbnail
github.com
8 Upvotes

r/icfpcontest • • Jul 23 '20

ICFPC-2020, team Just No Pathfinding, part 2.

Thumbnail
dastapov.dreamwidth.org
11 Upvotes

r/icfpcontest • • Aug 02 '20

ICFPC-2020 Organizers Release Their Source-Code

Thumbnail
github.com
7 Upvotes

r/icfpcontest • • Jul 03 '20

Spoilers?

5 Upvotes

ICFPC 2020 orgs just retweeted some cryptic tweet from a Russian astronomer (?). Is it a spoiler? Should we investigate?

https://twitter.com/icfpcontest2020/status/1278965948461056000


r/icfpcontest • • Sep 11 '12

ICFP 2012 contest final results

Thumbnail
icfpcontest2012.wordpress.com
2 Upvotes

r/icfpcontest • • Aug 09 '17

Team THIRTEEN ICFP Contest 2017 Writeup (visualizer, links to video)

Thumbnail
docs.google.com
8 Upvotes

r/icfpcontest • • Aug 08 '17

My Solo Solution - Lambda In Closure Act (Haskell)

Thumbnail
github.com
6 Upvotes