ICL: Input files

During each ICL session, there is an application and configuration name. The application name (contains only chars allowed in a filename) is determined at startup, and cannot be changed during one session (you have to restart). The configuration name (can contain a '/', exept at the beginning) however, can be changed any time during one session, with the command new_config. At startup, both names are initialised as follows:

• the application name is either the first argument to ICL, the value of the environment variable ICL_APPLICATION, or the interactive input from the user
• the configuration name is either the second argument to ICL (if any), the value of the environment variable ICL_APPL_CONF, or the interactive input from the user

For each application, we have several input files. The KB file and the BG file are fixed (ie the same for each configuration). The S file, the L file and the output files are fixed within one configuration. So whenever one switches to another configuration, the corresponding S and L files will be loaded.

None of the input files are mandatory. However, without KB file, you won't be able to do much. Also the L file will be necessary to learn rules. If no S file is given, the default settings are used.

Short overview of the files

• KB file: appl_name.kb
  This file must be in the current dir (where ICL is started). It's name is appl_name.kb (the application name and a postfix kb). It 's the knowledge base input. All the knowledge for one application is put in here.
  The file is divided in several blocks. Each block is surrounded by a begin(Name) and end(Name) fact, with Name either model(Nr) or background. You can have several blocks with the same name, but we recommand not to do this. We force the user to give each model a unique number. A model can contain for the moment only facts, the background any prolog clauses. It's the user's responsibility to ensure that there exists no infinite loops when calling a certain predicate.
  Note: When using the Runtime version, your input files will be interpreted on a line-by-line basis. Make sure each fact or rule in the KB file and BG file starts on a new line.
• BG file: appl_name.bg
  This is an optional file, where you can put all the clauses of the background. This is the same as using the background block in the KB file.
• S file: conf_name.appl_name.s
  This is the settings file, where the user can specify some specific settings (ie tuning the system). All the possibilities can be found here. If no S file is given, the default settings are used. (remark: don't forget the endpoint after each setting)
• L file: conf_name.appl_name.l
  This is the language file. All input needed by the language bias is in here. All the possible language biases can be found here.

Examples

• application muta, configuration ''

  	./muta.kb
  	./muta.bg
  	./muta.s
  	./muta.l
  

• application muta, configuaration 1_

  	./muta.kb
  	./muta.bg
  	./1_muta.s
  	./1_muta.l
  

• application muta, configuaration 1/

  	./muta.kb
  	./muta.bg
  	./1/muta.s
  	./1/muta.l
  

• application muta, configuaration /1
  

  	not allowed

Copyright 1997, Katholieke Universiteit Leuven, dept. Computerwetenschappen Information provider: KULeuven dept. Computerwetenschappen Comments for the authors: Wim Van Laer Page design: Wim Van Laer URL: http://www.cs.kuleuven.ac.be/input.html