Sunday, August 7, 2016
Announcing the leaderboard freeze
Our fridge have been repaired! The leaderboard is now frozen as planned. All submissions from now on will not be reflected in the leaderboard. However, other pages of the contest server, especially the “Solution Ranking” section in the “Problem Details” pages, will remain up to date until the end of the contest. Good luck!
Notification of the system change
We have detected a subtle glitch in our system, however, this will
not affect any of the contest activity including problem submissions,
solution submissions, and evaluations. We are now working on a fix.
(12:00 UTC, 7 Aug) Update: The glitch was that our fridge have failed, so we cannot freeze the leaderboard for the moment. We also have little choice but to give out all the sushi and sukiyaki we have kept in the fridge. It’s a little bit earlier than we’ve planned, but please accept these rewards and hang on for remaining hours.
(12:00 UTC, 7 Aug) Update: The glitch was that our fridge have failed, so we cannot freeze the leaderboard for the moment. We also have little choice but to give out all the sushi and sukiyaki we have kept in the fridge. It’s a little bit earlier than we’ve planned, but please accept these rewards and hang on for remaining hours.
Appologies on icfpcontest2016@googlegroup.org icfpcontest2016@googlegroups.com
We have found out that our contact e-mail address has been rejecting posts from non-members. Those who have tried to contact us via e-mail may have received following messages. We have now fixed our configuration.
We're writing to let you know that the group you tried to contact (icfpcontest2016) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post: ...
Our sincere appologies for the inconvenience.
Also note that some file types are blocked for this e-mail address. Again, if you have any problem, please do not hesitate to contact us, so that we can make our best effort to retrieve your valued source codes.
We're writing to let you know that the group you tried to contact (icfpcontest2016) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post: ...
Our sincere appologies for the inconvenience.
Also note that some file types are blocked for this e-mail address. Again, if you have any problem, please do not hesitate to contact us, so that we can make our best effort to retrieve your valued source codes.
Source code submission and how to win Judges' prize
Sixteen hours left till the end of the contest! We would like to ask you to review your team information (http://2016sv.icfpcontest.org/profile) before the contest ends, especially:
You need to submit source codes within 24 hours from the end of the contest. The easiest way is to upload your source code on a web server (e.g. your own web server, Dropbox or Google Drive, etc.). If you cannot provide a public URL, please leave it blank and send your source files into icfpcontest2016@googlegroups.com by the end of the contest. Please contact us if your source code is too large to send it via email.
Preferably, the source code URL should point to a single .tar.gz archive file. Judges will make our best effort to handle other formats. Put README.txt in the root directory of the submitted archive to nominate yourself for the Judges’ prize. Let us know how you have survived the contest!
- Contact email address
- Team member names
- Languages
- Source code URL
You need to submit source codes within 24 hours from the end of the contest. The easiest way is to upload your source code on a web server (e.g. your own web server, Dropbox or Google Drive, etc.). If you cannot provide a public URL, please leave it blank and send your source files into icfpcontest2016@googlegroups.com by the end of the contest. Please contact us if your source code is too large to send it via email.
Preferably, the source code URL should point to a single .tar.gz archive file. Judges will make our best effort to handle other formats. Put README.txt in the root directory of the submitted archive to nominate yourself for the Judges’ prize. Let us know how you have survived the contest!
How to solve origami 101 (crane) in 8 seconds
Our server solves origami 101 in 8 seconds by simulated annealing.
It should not be so hard!
Saturday, August 6, 2016
The idea behind the rate limits
Dear contestants,
You might have been feeling uncomfortable with the rate limits on the APIs. Well, we would like to support your efforts till the very end of the contest. We don't prefer to promise you optimistic rates and betray your expectations at the last moment of the contest, when you are in the final rush and need the server stability the most. We have prepared computer resources that are able to serve at these rates under any foreseeable circumstances in the future. Of course, unexpected things happen, but we have recovered from one of such cases.
We will do our best in keeping up the servers, so please enjoy the contest, and please find out the most blessed origami possible!
Meanwhile, here are some tips:
You might have been feeling uncomfortable with the rate limits on the APIs. Well, we would like to support your efforts till the very end of the contest. We don't prefer to promise you optimistic rates and betray your expectations at the last moment of the contest, when you are in the final rush and need the server stability the most. We have prepared computer resources that are able to serve at these rates under any foreseeable circumstances in the future. Of course, unexpected things happen, but we have recovered from one of such cases.
We will do our best in keeping up the servers, so please enjoy the contest, and please find out the most blessed origami possible!
Meanwhile, here are some tips:
- Cache your blob lookup results.
- Take record of the best solution you have submitted and its resemblance to each problem, and postpone new submissions until you have made improvements.
More informative server responses for invalid submissions
It is our pity that you might have suffered from too many of the blunt invalid solution messages. In fact, each of those invalid origami had contained weak but certain portion of prayer for better error message so that the contest server have accumulated the enough enchantment to return more informative error diagnostics:
We wish this update help you as you are going to face harder problems.
We wish this update help you as you are going to face harder problems.
Subscribe to:
Posts (Atom)