Python-based HEX implementation for a fragment of the HEX language and a subset of features.
Clone or download
peschue Adding documentation about how to call hexlite (#6)
in particular mention how to use -- to overcome the problem of plugin arguments vs HEX input files
Latest commit 08cc8a6 Dec 14, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
acthex small fixes here and there May 28, 2018
bin added argument to hide models during execution Oct 19, 2018
dlvhex cherry-picked parts of "some refactoring to make acthex feasible with… Oct 9, 2018
hexlite making conversion more robust in case of unparseable values coming fr… Oct 10, 2018
plugins many fixes in test plugin and test program May 28, 2018
tests first draft of acthex tests finished May 28, 2018
.travis.yml we install only python 3, so python = python3 Oct 24, 2018
LICENSE GPL Apr 22, 2017 fixing installation and support of build on Ubuntu 16.04 Jun 1, 2017
README Adding documentation about how to call hexlite (#6) Dec 14, 2018 Adding documentation about how to call hexlite (#6) Dec 14, 2018
meta.yaml version 1.0.0 Oct 24, 2018

Build Status codebeat badge Anaconda-Server Badge

Hexlite - Solver for a fragment of HEX

This is a solver for a fragment of the HEX language and for Python-based plugins which is based on Python interfaces of Clingo and does not contain any C++ code itself.

The intention is to provide a lightweight system for an easy start with HEX.

The vision is that HEXLite can use existing Python plugins and runs based on the Clingo python interface, without realizing the full power of HEX.

The system is currently under development and only works for certain programs:

  • External atoms with only constant inputs are evaluated during grounding in Gringo
  • External atoms with predicate input(s) and no constant outputs are evaluated during solving in a clasp Propagator
  • External atoms with predicate input(s) and constant outputs that have a domain predicate can also be evaluated
  • Liberal Safety is not implemented
  • Properties of external atoms are not used
  • If it has a finite grounding, it will terminate, otherwise, it will not - as usual with Gringo
  • FLP Check is implemented explicitly and does not work with strong negation and weak constraints
  • FLP Check can be deactivated

A manuscript about the system is under preparation.

In case of bugs please report an issue here:

  • License: GPL (3.0)

  • Author: Peter Schüller

  • Available at PyPi:

  • Installation with Conda:

    The easiest way to install hexlite is Conda.

    First you need to install the clingo dependency:

    $ conda install -c potassco clingo

    Then you install hexlite:

    $ conda install -c peterschueller hexlite

    (If you wonder why we do not automatically install clingo as a dependency: certain conda restrictions prevent that clingo is automatically installed unless the potassco channel is manually added by the user.)

    Then you test hexlite:

    $ hexlite -h

  • Installation with pip:

    This will download, build, and locally install Python-enabled clingo modules.

    • If you do not have it: install python-pip: for example under Ubuntu via

      $ sudo apt-get install python-pip

    • Install hexlite:

      $ pip install hexlite --user

    • Setup Python to use the "Userinstall" environment that allows you to install Python programs without overwriting system packages:

      Add the following to your .profile or .bashrc file:

export PYTHONUSERBASE=~/.local/
export PATH=$PATH:~/.local/bin
  • Run hexlite the first time. This will help to download and build pyclingo unless it is already usable via import clingo:

    $ hexlite

    The first run of hexlite might ask you to enter the sudo password to install several packages. (You can do this manually. Simply abort and later run hexlite again.)

  • Ubuntu 16.04 is tested

  • Debian 8.6 (jessie) is tested

  • Ubuntu 14.04 can not work without manual installation of cmake 3.1 or higher (for buildling clingo)

Running Hexlite on Examples in the Repository

  • If hexlite by itself shows the help, you can run it on some examples in the repository.

  • Hexlite needs to know where to find plugins and what is the name of the Python modules of these plugins

    • The path for plugins is given as argument --pluginpath <path>.

      This argument can be given multiple times. You can use absolute or relative paths.

    • The python modules to load are given as argument --plugin <module> [<argument1> <argument2>].

      Multiple plugins can be loaded. Each plugin can have arguments.

      !ATTENTION!: If you specify the HEX input file after --plugin <module>, it becomes the argument of the plugin. In this case, you need to

      • specify the HEX input files before the other arguments or
      • indicate end of the argument list with the -- option.
  • To run one of the examples in the tests/ directory you can use one of the following methods to call hexlite:

$ hexlite --pluginpath ./plugins/ --plugin testplugin -- tests/extatom3.hex
$ hexlite tests/extatom3.hex --pluginpath ./plugins/ --plugin testplugin
$ hexlite --pluginpath=./plugins/ --plugin=testplugin tests/extatom3.hex

Developer Readme

  • For developing hexlite without uploading to anaconda repository:

    • Install clingo with conda, but but do not install hexlite with conda.

    $ conda install -c potassco clingo

    • checkout hexlite with git

    $ git clone

    • install hexlite in develop mode into your user-defined Python space:

    $ python3 develop --user

    • If you want to remove this development installation:
$ python3 develop --uninstall --user
$ rm ~/.local/bin/hexlite

(Installed scripts are not automatically uninstalled.)

  • Build and upload new version to pip and conda:

    • Update version in

    • Build pypi source package

    $ python sdist

    • Verify that dist/ contains the right archives with the right content (no wheels etc.)

    • Upload to pypi

    $ twine upload dist/*

    • Update version in meta.yaml.

    • Build for anaconda cloud

    $ conda build .

    (get upload command from last lines of output)

    • Verify that archive to upload contains the right content (and no backup files, experimental results, etc...)

      $ anaconda upload <path-from-conda-build>