{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/156a9300f7d83236d4edd631c779a14c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"156a9300f7d83236d4edd631c779a14c","url":"https://api.github.com/users/Janzert","login":"Janzert","id":392930},"labels":[],"assignee":null,"updated_at":"2011-11-01T08:22:20Z","comments":3,"closed_at":null,"url":"https://api.github.com/repos/aichallenge/aichallenge/issues/344","body":"The current rules are essentially unchanged from the last few contests. There's probably more but a couple that I'm looking at right now that really need updating are:\r\n\r\n * You may not write to files. You may however read from files within your submission directory, which will be the current directory.\r\n * Use of multiple processes or OS threads are prohibited.\r\n\r\nNeither of these are things we actually do or can prohibit because there are language *runtimes* that break them. The two examples off the top of my head are mono writing files and java spawning processes. Java for sure and IIRC mono both crash if they aren't allowed to do so.\r\n\r\nInstead I think we should have something along the lines of:\r\n\r\n * setting a smallish limit (10MB?) on the size of files written and explain that they won't be preserved past the end of the game\r\n * setting the limit on threads/processes to what is required by the runtimes and prohibit active computation on more than one at a time","html_url":"https://github.com/aichallenge/aichallenge/issues/344","number":344,"title":"Update contest rules","id":2086202,"created_at":"2011-10-29T07:47:37Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/9b00a4d1bbb97c8a77b5fa7764e9afbd?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"9b00a4d1bbb97c8a77b5fa7764e9afbd","url":"https://api.github.com/users/mleise","login":"mleise","id":609447},"updated_at":"2011-11-01T08:22:20Z","url":"https://api.github.com/repos/aichallenge/aichallenge/issues/comments/2587874","body":"+1, but let me give a real answer. I think details on how large the written files may become don't need to be in the rules. There is simply no point in writing to files. They are not preserved and we grant way more RAM than what 10 MB slow swap would represent. Maybe put it in parenthesis after a simple one-liner, for those that uploaded a bot that writes a log and wonder if it will be disqualified or crash :)\r\n\"Active computation\" sounds good at first, but I wonder what happens with Java's JIT compiler. Assuming not all classes are used (and compiled) in turn \"0\", this may result in additional cores used as soon as classes for path finding, a math library etc. are accessed. Otherwise it is a good idea to simply check for wall_time >= cpu_time. If you used more cpu time than wall time, you must have used more than one core actively.","id":2587874,"created_at":"2011-11-01T08:22:20Z"}}