Participating Planners

The following lists all planners that participated in the IPC. Note that our IPC booklet includes papers describing the participating planners.

Nr.Participant Git Repo Singularity
1LiloTane ANU Gitlab container
2SIADEX ANU Gitlab container
4HyperTensioN ANU Gitlab container
5PDDL4J-TO ANU Gitlab container
6PDDL4J-PO ANU Gitlab container
7pyHiPOP ANU Gitlab container

For each planner its source code can be downloaded as well as its singularity container, which is is ready-to-go planner, i.e., fully configurated as for the IPC. If you plan to install singularity using Linux/ubuntu, note that installing 'singularity' from the command line will install a computergame. To install the containerization platform instead, please refer to instructions on singularity's official webpage, e.g., for version 3.5 (although there are also newer versions!).

You can build each planner by running singularity build ../image.sif Singularity in the cloned folder. In order to run a planner that is packaged as a singularity container, you need to create a folder in which the planner is executed. This can be your current folder, but be aware that the planner may write files into this folder. If you run the containers on a cluster, it is advisable to create one such folder per execution of the planner - else the written files may interfere. Assure that this folder has the absolute path PATH. Note that the HDDL files also need to reside in the specified PATH location. You can then run the planner with singularity run -H PATH -C image.sif domain.hddl problem.hddl planner.out TIME MEM SEED, where TIME is the time limit in seconds, MEM is the memory limit in MB, and SEED is a seed. Note that the planners may exceed time and memory limits as these are only informational to the planner. If you need to enforce limits, you need to do this yourself.

If you follow these instructions and run into issues or have suggestions on how to improve this (admittedly short) description, let us know!

Updated Planners

All planners as above are exactly those who participated at the IPC. If you plan to conduct experiments, you could either use "exactly those versions", or -- preferably -- the newest version available. Generally, you should always search on the developers' webpages for the newest (stable) version to compare against; contact them if necessary.

After the IPC 2020, two competitors (see below) have updated their planners based on the IPC's results. This includes bugfixes and minor performance improvements. If you, for some reason, want to use the exact versions of the planner as they were run in the IPC, do not use these two (as noted above). In all other cases, we recommend to use the updated versions as they are objectively better. (But, also as said, you might also reach out to the authors directly to obtain an even newer version if one exists.)

Also note that HTN2STRIPS (see below) did not compete in the IPC 2020. The planner was registered for the competition, but did not complete its software integration in time and was thus disqualified. After the competition, we continued this integration using the state of the code at the time of the IPC 2020. We provide this container simply to have a complete picture of the available planners at the time of the IPC.