Logical Algorithms

Logical Algorithms, Harald Ganzinger and David McAllester. ICALP 2002.

It is widely accepted that many algorithms can be concisely and clearly expressed as logical inference rules. However, logic programming has been inappropriate for the study of the running time of algorithms because there has not been a clear and precise model of the run time of a logic program. We present a logic programming model of computation appropriate for the study of the run time of a wide variety of algorithms.

So, there are two main styles in logic programming. The first is Prolog-style goal-directed, or backwards, search. The idea is that you have a set of rules, and a goal, and you nondeterministically choose rules that might have proven that goal, trying to find a sequence of deductions that could have proven this goal. It's called backwards search since you are trying to reason backwards from the goal towards a full proof.

The other style is, naturally, called forwards search (confusingly, this is also called the inverse method in theorem proving). The idea is that you have a goal, and some rules, and a starting set of facts. You then apply the rules to the facts you have, enlarging your database of facts and enabling more deductions. You keep doing this until either you discover the goal you were trying to prove in the database of facts, or the database saturates (ie, no more deductions are provable) and the goal is unprovable. The idea is that your database is an implicit data structure, which you update as part of the search. This makes forwards search a particularly natural method when you're trying to compute closures -- graph algorithms, dataflow analyses, that kind of thing.

While we've discussed applications of forward logic programming before, I thought it might be good to link to a discussion of the methodology of how to specify algorithms as forward logic programs and analyze their complexity.

The language in this paper permits deletion of facts from the database, which is unfortunately a non-logical operation -- in clasical and intuitionistic logic, deduction can only increase the number of facts you know. But with a change of logic, it can be made logical. That'll be the next paper I post a link to. :)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Forward search against real time

You keep doing this until either you discover the goal you were trying to prove in the database of facts, or the database saturates (ie, no more deductions are provable) and the goal is unprovable.

Or until you decide you have taken too long and cut the search short.

Deletion of facts from the database

Isn't it what non-monotonic logic is all about ?

Yep

Delete, or update...

I highly recommend looking at the tutorial for FLORA-2, a combined F-Logic/HiLog/Transaction Logic system that runs on top of XSB. There is an extension to FLORA-2, "Persistent Modules," that associates FLORA-2 modules with ODBC data sources. The result seems to be a very nice non-monotonic programming system (thanks to the Transaction Logic aspect of FLORA-2) that can talk to any database that you have ODBC support for.

Yep!

The next paper will be about using linear logic programming to specify algorithms, which is indeed a non-monotonic logic.