Participant submission procedure

Application

To register for the competition, send an email to aspcomp2011 _at_ mat.unical.it specifying:

• the name of your team;
• names and affiliation of the participants (institution, research group);
• whether the team will participates to the system or to the model competition, or both.

As soon as you will get credentials for entering the Competition server, you will get a Linux home directory having a folder structure described next. A sample home directory tree can be found here.

Instructions for testing and submitting systems and benchmarks

Your home directory in the Competition server contains a subdirectory submitted. Only files in this directory will be processed during the Competition.

The submitted directory contains a subdirectory for each benchmark. Each of these directories must comprise all files required for solving a specific benchmark. In particular, there must be a file run, which will be invoked during the Competition. This file can be a script invoking a binary executable, possibly using other scripts for pre- or post-processing. All files invoked by run must be placed in the directory containing the run file, or in one of its subdirectories. Moreover, only relative paths must be used in all scripts; note that this is a strong requirement, since the Competition would be executed on a different machine. During the Competition, the run file will be invoked with two command-line arguments. The first argument is the maximum integer which is sufficient for solving the input instance. The second argument is the maximum nesting level of function symbols which is sufficient for solving the input instance. These arguments can be passed to the binary executable or just ignored. Instances will be provided via standard input. The output must be printed in standard output, according to the format specified in the benchmark description. Examples of scripts will be provided in each benchmark directory.

In addition to the subdirectories for benchmarks, the submitted directory also contains a subdirectory System for the system competition. Even in this case, the run file will be invoked during the Competition. A third additional arguments will be specified in the command-line, which will be a comma-separated list of predicate names. These predicates must be used for representing witnessing models of satisfiable instances; the extensions of these predicates must be printed in standard output. Examples of scripts will be provided in the System directory.

The submission process will be performed by properly invoking the submit tool. This tool requires a command-line parameter specifying either System or the name of a directory containing a benchmark solution (just the name, not the complete path). Once a system or a benchmark are submitted, any modification to the associated directories is prevented. At any time, a participant can invoke the unsubmit tool to retire a submitted directory and get back the grant of modifying its content.

Examples

To submit your System directory, just write:

$ submit System

The System directory is no more editable. To undo your submission, type:

$ unsubmit System

IMPORTANT: The submitted directory will be accessible only after the benchmark submission closure. During the benchmark submission phase, participants will be provided with a try directory, structured as submitted. This directory can be used for testing systems and benchmark encodings.