Leo's Parallal ARchitecture & Datastructures (LeoPARD)
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
scripts
src
.gitignore
LICENSE
Makefile
README.md
build.sbt
leo.sh
pom.xml

README.md

LeoPARD

Leo-III's Parallel ARchitecture and Datastructures

This project contains the data structure framework LeoPARD underlying the Leo-III prover.

In the Leo-III project, we design and implement a state-of-the-art Higher-Order Logic Theorem Prover, the successor of the well known LEO-II prover [1]. Leo-III will be based on ordered paramodulation/superposition. The prover also integrates and extends ideas from LEO-I [2] and the OANTS [3,4] blackboard mechanism. In contrast to LEO-II and LEO-I, we replace the internal term representation (the commonly used simply typed lambda-calculus) by a more expressive system supporting type polymorphism. In order to achieve a substantial performance speed-up, the architecture of Leo-III will be based on massive parallelism (e.g. And/Or-Parallelism, Multisearch) [5]. The current design is a multi-agent blackboard architecture that will allow to independently run agents with our proof calculus as well as agents for external (specialized) provers. Leo-III will focus right from the start on compatibility to the widely used TPTP infrastructure [6]. Moreover, it will offer built-in support for specialized external prover agents and provide external interfaces to interactive provers such as Isabelle/HOL [7]. The implementation will excessively use term sharing [8, 9] and several indexing techniques [10, 11]. Leo-III will also offer special support for reasoning in various quantified non-classical logics by exploiting a semantic embedding [12] approach.

As a test and for illustration purposes, a small executable can be created than runs a basic propositional reasoning process. After the public release of Leo-III further features of this prover will be made available in LeoPARD.

Further information can be found at the Leo-III Website.

Features

  • Basic standard data structures for logical reasoning included (such as Terms, Clauses, Literals, Signatures, ...)
  • Efficient higher-order term representation based on the polymorphically typed Lambda-Calculus (employing Spine notation, explicit substitutions and perfect term sharing)
  • Parser for every TPTP syntax dialect (including CNF, FOF, TFF, TFA, TH0), preliminary support for TFF1-draft dialect
  • Translation module for transforming each parsed formula to an equivalent Lambda-Term
  • Backward translation of internal terms and formulae to TPTP THF compatible representation
  • Signature with all TPTP-compatible (fixed/defined) constants available
  • Generic multi-agent design for massive parallel reasoning
  • Generic templates for the employment of external reasoners included (works best with SZS status compatible reasoners)
  • Blackboard architecture for agent communication and knowledge sharing

External prover support

An experimental external prover support is included in this version. The command-line parameter "--with-prover" can be set to "leo2", "satallax" or "remote-leo2". In the first two cases the provers need to be installed locally and their paths (the path to the executable) need to be accessible via the environment variables $LEO2_PATH and $SATALLAX_PATH (respectively). For the remote-leo2 call, internet connection needs to be active.

Related Documents

Required Dependencies

Leo III needs Java 1.7 to run. Scala 2.11.X is required to build and run the project. Maven will automatically download scala and further dependencies. Alternatively, Scala can be downloaded at Scala-lang.org.

Building the project

Maven manages the build process of Leo-III. Information about downloading and installing Maven can be found at the download section of the maven website.

The project is compiled and built into an executable .jar file usng

> mvn compile assembly::single

Or, alternatively, the makefile can be used. Invoking

> make

will result in the same .jar

All test suits are ran by

> mvn test

The compiled test class files will be placed at ./target/test-classes/.

For the tests it is important that the project is placed in a path where each directory does not contain any blank spaces. Otherwise the tests are not executed.

The sole compilation process can be started by typing

> mvn compile

The compiled files (class files) will be placed at ./target/classes/.

Project's current structure

This section is a stub. It will be expanded in the future.

└──leo                     -- Where the Main executable is located, root package
    ├── agents             -- Specification of agents
    │   └── impl           -- Implementation of agents
    ├── datastructures     -- root package for all base data structures
    │   ├── blackboard
    │   ├── context
    │   ├── impl           -- Most of the implementations are located here
    │   ├── term
    │   └── tptp           -- Internal syntax representation of TPTP
    └── modules            -- All sorts of functionality modules
        ├── churchNumerals -- old package, most likely to be removed soon
        ├── normalization
        ├── output         -- Output and logging functionality
        ├── parsers        -- Input parsing
        ├── proofCalculi
        └── visualization