Systems

A team may use a system among these:

• SWI-Prolog: http://www.swi-prolog.org
• GNU Prolog: http://gprolog.org
• Ciao Prolog: http://ciao-lang.org
• ECLiPSe Prolog: http://eclipseclp.org
• XSB Prolog: http://xsb.sourceforge.net
• Potassco: http://potassco.sourceforge.net
• Picat: http://picat-lang.org
• MiniZinc: http://www.minizinc.org
• IDP: https://dtai.cs.kuleuven.be/software/idp

Some sample problems and solutions can be found at https://sites.google.com/site/prologcontest2017/.

In case any team wants to use another system, they must contact the organizers in advance and provide assistance in installing and testing the system. Additionally, they must provide solutions for the sample problems.

• For each problem, a submitted program must have the main name as specified by the problem description and the schema explained in Participation page. In case a team submits programs by using a USB stick the extension name must correctly indicate the used language/system. For ASP system the extension is ".lp"; for Minizinc the extension is ".mzn"; for Prolog systems the extension name is ".pl"; and for Picat the extension is ".pi".
• For each problem, a set of instances is used to test submitted programs. A smaller set of the test instances and their sample outputs will be made available online during the competition.
• In order to evaluate submitted programs we will use a Docker image where all systems are installed in. Installing and using the Docker image is not necessary for teams, but it is recommended. For more information on how to install it or pull it from the DockerHub and use your favourite system inside the Docker image, check https://github.com/lpcp-contest/docker-lpcpsys .
• Submitted programs will be tested using the run script provided in the Docker image. It is recommended that the teams install the Docker image before the competition and try their system of choice using the sample problems mentioned above. That run script will start program-runs using the following command-line templates:

# SWI Prolog

swipl -g "main,halt." prog1.pl instance1.pl

# GNU-Prolog

gprolog --consult-file prog1.pl --consult-file instance1.pl --query-goal main

# Ciao Prolog

ciaosh -u prog1.pl -u instance1.pl -e "main,halt."

# Eclipse CLP

eclipse -e main -f prog1.pl -f instance1.pl 

# XSB Prolog

xsb -e "[prog1], [instance1], main, halt."

# Clingo (with Lua support enabled)

clingo prog1.lp instance1.pl 

# Picat

picat prog1.pi instance1.pl 

# Minizinc

minizinc prog1.mzn instance1.dzn 

• All outputs must be sent to the standard output in the format specified by the problem description.
• If a program fails to give a correct answer or fails to solve an instance in 90 seconds, the team may be notified by email (only for the on-site track) and can submit another program. Note that in case of iterative solving of optimization problems (e.g., clingo's optimization statements), the program execution has to finish within the time limit and the last answer will be considered as the solution for evaluations.