Problem Submission Specification: Input, Output, Checking

Package Submission Templates

Preliminary submission (see Example) can be done by providing problem name and problem specification only; we encourage to provide an ASP encoding and sample instances also.
Complete problem specifications (see Example) have to be packaged in a single compressed archive named benchmark_name-contributor_name.zip (or tar.gz) containing:
1. a benchmark_name.spec.txt file containing the textual problem description (a template is available, see below);
2. a benchmark_name.enc.asp file containing a proposed encoding in ASP for the problem (details about the language will follow);
3. a folder named checker containing the sources of a correctness checker together with a README.txt file containing the instructions for (possibly building and) running it;
4. a folder named samples containing some instances (one instance per text file).

benchmark_name and contributor_name should be substituted with their actual value.