Final Competition: Dates, Rules, EC2 Credit

[ssanner]

Hi all,

According to the Doodle poll:

  http://doodle.com/ebn9997wpzuzz7xu

**June 9-13, 2014** is the only week that works for all competitors, so this will be the final competition week.

Recall the final competition rules posted previously on this list and included at the end of this post.  Some additional details:

- The planner freeze and domain / 1st instance release will occur on June 6 (UTC, 12:01am).

- Around June 1st we'll post a Doodle so people can select a date and UTC time when we'll start their server/port (up to 3 if running multiple planners) and email them all information required to compete.

- We'll give competitors 24 hours + 30 minutes instance download/setup time before shutting down their server/port.  If competitors need a little more time, they should email us with the reasons... we'll note this when reporting final competition results.

- All competitors should use a single EC2 m3.large instance, see https://aws.amazon.com/ec2/pricing/

- IP addresses of clients will be logged and verified to originate within EC2.

- We'll provide each competing group with a coupon for $100 credit on EC2 (thanks to EC2 for providing an AWS grant for the competition).  Send me an email to obtain this.

- Please note the post-competition responsibilities of competitors below.

Cheers,

Scott and Marek

===

Final competition Rules:

(a) Competition week: The final competition will take place over a one week period where competitors will sign up for a 24 hour time slot during this period.  

(b) Planner freeze and domain release: 3 days prior to the start of the one week competition period, a planner freeze will be put in effect -- no planner modifications can be made from this point on (which includes manual parameter tuning, algorithm changes, or other performance modifications).  At the time of the planner freeze we will provide a link to the 8 competition domains and one associated instance for each domain.  If competitors have *parse errors* or *planner crashes*, they are allowed to fix these issues during the planner freeze period so long as they document all planner modifications and post their *full list of changes* to this email list.

(c) 24 hour Competition slot: The full competition domain and instance list will be released to competitors via a private web link at the start of their chosen 24 hour competition slot.  

(d) Post-competition: all competitors need to sign a document saying that they have honored the rules above (there will a section to explain any variations, e.g., to list changes on account of debugging).  Competitors also need to submit an archive of their source code to the organizers with instructions on how to run the planner to reproduce competition results.  (The organizers will not publicly release this code.)  

(e) Final results: released at ICAPS 2014 (June 21-26) and posted to the IPPC website immediately thereafter.

[Andrey Kolobov]

Hi all,

I was going to suggest that the participants send the code, the executable, and the command line with all the arguments to be used during the competition right *before* the freeze, not *after* the competition. If one needs to fix a crash-causing bug during the freeze, they would additionally send Scott and Marek the fixed version of the code and executable (the command line would stay the same). Scott and Marek would then be able to see the changes by simply running diff.

Any objections?

Cheers,

Andrey

--
You received this message because you are subscribed to the Google Groups "IPPC 2014 (DISCRETE TRACK)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ippc-2014-discr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.