Commit c333ec8e authored by David Speck's avatar David Speck

ipc2018 version

parents
# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.lo
*.so
# Packages #
############
# it's better to unpack these files and commit the raw source
# git has its own built in compression methods
*.7z
*.dmg
*.gz
*.iso
*.jar
*.rar
*.tar
*.zip
# Logs and databases #
######################
*.log
*.sql
*.sqlite
# OS generated files #
######################
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
ehthumbs.db
Thumbs.db
# Tmp files #
#############
*~
*.tmp.*
*.pyc
# Symple
Symple performs A* search based on Edge-Valued Multi-Valued
Decision Diagrams (EVMDDs). It supports zero, unit, constant and
state-dependent action costs.
Symple is is built on top of
[Fast Downward](http://www.fast-downward.org/),
[SymBa](https://fai.cs.uni-saarland.de/torralba/software.html)
and [MEDDLY-0.18](https://meddly.sourceforge.io/).
Therfore, it it is made available under the GNU Public License (GPL).
## 1. Compiling Symple
The command
```sh
$ git clone https://gkigit.informatik.uni-freiburg.de/dspeck/symple.git <dirname>
```
will create a clone of Symple master repository in directory "dirname".
To build Symple run the following command.
```sh
$ cd <dirname>
$ ./build
```
## 2. Running Symple
Symple is callable with several configurations.
### 2.1 Defaul Configuration (IPC-18)
Starting Symple with defaul configurations (bidirectional search, 100k node
limit per transition relation):
```sh
$ ./plan <domain> <problem> <plan-output-file>
```
### 2.2 Predefined Configurations
Starting Symple with predefinied configurations:
```sh
$ .src/plan-ipc <planner> <domain> <problem> <plan-output-file>
```
You can choose between the following predefined configurations for the "planer"
parameter, where the term stands for the search direction and the number for
the node limit of the transition relations.
+ **Bidirectional Search**: symple, symple0, symple10000, symple25000, symple50000, symple100000, symple200000
+ **Progression**: symplePro, symplePro0, symplePro10000, symplePro25000, symplePro50000, symplePro100000, symplePro200000
+ **Regression**: sympleReg, sympleReg0, sympleReg10000, sympleReg25000, sympleReg50000, sympleReg100000, sympleReg200000
### 2.3 Userdefined Configurations
In general, it is possible to define new configurations for Symple. The easiest
way is to insert a new predined configuration to the [downward](src/search/downward) file.
For more information, please visit the [Fast Downward](http://www.fast-downward.org/)
website.
## 3 Benchmarks
+ [Here](https://bitbucket.org/planning-researchers/classical-domains), you can find a benchmark set containing of former IPC domains.
+ [Here](https://gkigit.informatik.uni-freiburg.de/dspeck/SDAC-Benchmarks), you can find a benchmark set containing of domains with state-dependent action costs.
Bootstrap: docker
From: ubuntu
%setup
## The "%setup"-part of this script is called to bootstrap an empty
## container. It copies the source files from the branch of your
## repository where this file is located into the container to the
## directory "/planner". Do not change this part unless you know
## what you are doing and you are certain that you have to do so.
REPO_ROOT=`dirname $SINGULARITY_BUILDDEF`
cp -r $REPO_ROOT/ $SINGULARITY_ROOTFS/planner
%post
## The "%post"-part of this script is called after the container has
## been created with the "%setup"-part above and runs "inside the
## container". Most importantly, it is used to install dependencies
## and build the planner. Add all commands that have to be executed
## once before the planner runs in this part of the script.
## Install all necessary dependencies.
apt-get update
apt-get -y install cmake g++ make python automake autoconf libtool time gawk flex bison
## Build your planner
cd /planner
./build -j4
%runscript
## The runscript is called whenever the container is used to solve
## an instance.
DOMAINFILE=$1
PROBLEMFILE=$2
PLANFILE=$3
## Call your planner.
/planner/plan $DOMAINFILE $PROBLEMFILE $PLANFILE
## Update the following fields with meta data about your submission.
## Please use the same field names and use only one line for each value.
%labels
Name Symple-1
Description Symple performs a bidirectional A* search based on Edge-Valued Multi-Valued Decision Diagrams (EVMDDs).
Authors David Speck, Florian Geißer and Robert Mattmüller <speckd,geisserf,mattmuel>@informatik.uni-freiburg.de
SupportsDerivedPredicates no
SupportsQuantifiedPreconditions no
SupportsQuantifiedEffects no
#! /bin/sh
#source /opt/centos/devtoolset-1.1/i386/enable
#module load libs/gcc-4.7.2/i386
cd src
./build_all "$@"
cd ..
#! /bin/bash
echo "$@"
"$(dirname "$0")"/src/plan-ipc-18 symple100000OPT "${@:1}"
GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.
"The Library" refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.
An "Application" is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.
A "Combined Work" is a work produced by combining or linking an
Application with the Library. The particular version of the Library
with which the Combined Work was made is also called the "Linked
Version".
The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.
The "Corresponding Application Code" for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified
version:
a) under this License, provided that you make a good faith effort to
ensure that, in the event an Application does not supply the
function or data, the facility still operates, and performs
whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of
this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from
a header file that is part of the Library. You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that the
Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this license
document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that,
taken together, effectively do not restrict modification of the
portions of the Library contained in the Combined Work and reverse
engineering for debugging such modifications, if you also do each of
the following:
a) Give prominent notice with each copy of the Combined Work that
the Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this license
document.