Event Log

NOT IMPLEMENTED (except diagnostics).

Although the major characteristics of a reduction are recorded in the reduction file, it may also be useful to have an ASCII record of the detailed sequence of events. The event log file serves this purpose. The level of detail with which events are logged can be adjusted to taste using the following parameters. The available classes being as follows:

    - TUNE_DIAGNOSE, used when a bug is suspected to log information
      of potential use to the maintainer of the package.

    - FULL, comprehensive event/problem/tuning/result/parameter
      logging.  All categories except DIAGNOSTIC.

    - INTERACTIVE, all user input and task (to screen) output.

    - PROBLEM, all problem reports and the users choices.

    - TUNING, all performance/parameter tuning information.

    - PARAMETERS, values of all active parameters.

    - BRIEF, only major information such as data frame file
      names are logged.

    - NONE, no logging file is produced. This option should not
      be used in normal circumstances.

Logged messages consist of type tags followed by a variable length message text. They may be examined using any standard editor.