This web will not be start to update information until 18th February

Build Status (19:36 on March 27, 2018)

The following table shows an overview of the last time we tried to build all planners. The revision in each cell shows the one that the build was based on. The color shows the status of the build. If your planner does not have a green "success" status in a track you want to participate in, please click on your team's row for more details and analyze the linked log files. This page will be updated about once a day. To test your changes locally, please follow the instructions on https://ipc2018-temporal.bitbucket.io.

We use the demo submission provided by the classical tracks to show the process. The code is available on bitbucket ( https://bitbucket.org/ipc2018/demo-submission). Our demo submission wants to participate in the optimal, the satisficing, and the cost-bounded track, so it has three branches ipc-2018-seq-opt, ipc-2018-seq-sat, and ipc-2018-seq-cbo. You can see that it passes the tests for the satisficing and the cost-bounded track but fails on one instance of the optimal track. Clicking on the row and investigating the logs of the failed instance shows the reason for this: the configuration uses LM-cut which does not support conditional effects.

Team Saticficing Track
ipc-2018-temp-sat
On Board Track
ipc-2018-temp-on-board
CP4TP

Revision:d886f463

Build:

Benchmarks:

Revision:e13cf1f5

Build:

Benchmarks:

TFLAP

Revision:e3bb0eb5

Build:

Benchmarks:

Revision:036bb290

Build:

Benchmarks:

TemPorAl

Revision:c2c5de78

Build:

Benchmarks:

Revision:?

Build:

n/a

Benchmarks:

n/a
What do the colors mean and what should I do about it?
Building the singularity container and executing it on a test case was successful.
Building the singularity container was successful but executing it on a test case failed. Analyze the log files linked in the table or contact us for help.
Building the singularity container failed. Analyze the log files linked in the table or contact us for help.
The branch for this track was not detected in this repository. If you want to participate in this track, add a branch with the name shown in the column header to your repository.