Did you know ... | Search Documentation: |
Pack flux -- prolog/indigolog/readme.txt |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % % FILE : readme % DATE : January 2007 % AUTHOR : Sebastian Sardina & Stavros Vassos % EMAIL : {ssardina,stavros}@cs.toronto.edu % WWW : www.cs.toronto.edu/~ssardina www.cs.toronto.edu/cogrobo % DESCRIPTION : top-level readme file %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
This is the root of the IndiGolog system. There are a few things you should know before running IndiGolog:
(0) Before you can run anything, you will need to read "install".
(1) The files of the implementation are scattered among many different directories. Here is the structure starting from the initial directory:
(2) Most of the code was designed and tested with the SWI Prolog system (http://www.swi-prolog.org/). Nevertheless, the whole architecture should also run with ECLIPSE Prolog (http://eclipse.crosscoreop.com/) which sometimes is needed when the application uses constraint programming.
(3) Each example application has its own sub-directory inside the Examples top-level directory. By convention, an application is loaded by consulting a file with a name of the form "main_xxx.pl" where xxx denotes the specific Prolog platform. For example, main_swi.pl is the file to load if using SWI Prolog and main_ecl.pl is the file to load if using ECLIPSE Prolog instead.
(4) There are three example applications that work as simulations. You should try to run these before trying IndiGolog on a real platform (such as on a real robot, on the Internet, etc.).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % EOF: readme %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%