## System Area Help

E-Mail Comments to: opencyc-doc@cyc.com
Copyright© 1997-2002 Cycorp. All rights reserved.

The System Area provides detailed information about the system settings of the current CYC® image, operations queues, and transcripts, as well as allowing the user to perform operations such as halting the CYC® image or loading CYC® patches.

### System Settings

"Current machine" shows the machine the CYC® image is running on.

"Current image number" shows the particular image number (uniquely identified by the date the CYC® image was started up on this particular machine). For example,

    	CLIO-1-19970505093744

means that the CYC® image was started up on Clio on May 5, 1997 at 9:37:44am.

"Image start time" displays the date and time the image was started and how long the image has been up and running.

"Current KB" lists the current version of the Knowledge Base, and will be updated when KB operations are loaded into the current CYC® image. Generally, a new CYC® image will be started up with a whole-number KB version (this number appears next to "KB" in the System Status frame at the bottom of the screen). Then, the number to the right of the decimal will match the total number of trancript operations that have been read (line #1 below). For example,

    	93.1064

would usually mean that the current image was started up with KB 93, and a total of 1064 operations have been read (but not necessarily processed). To see how many operations have been processed, see the Operations Queues section below for an explanation.

"System and patch level" lists the current version of the SubL code, including the patch level. For example,

            41.19

means that the CYC® image is based on version 41 of the SubL code, and the patch level (number of updates to this version of the SubL code) is 19.

C, NT, LISP (LispWorks/Allegro) images: clicking on "here" in the tagline at the bottom of this section will halt the CYC® image; there is a safety confirmation built into this option, since unintentionally halting the CYC® image will most likely have undesired consequences. LISP (Genera) images are generally not halted using the HTML interface; instead, LISP (Genera) machines are controlled via the command line interface on the LISP machine, which is best left up to those familiar with the LISP (Genera) machines.

LISP (Genera) images: clicking on "here" in the tagline at the bottom of this section will load patches, effectively bringing the SubL code up-to-date for the CYC® image. Loading patches is part of the CYC® Agenda's job, though it is occasionally necessary or desirable to load them by hand. C, NT, and LISP (LispWorks/Allegro) images do not load patches, instead catching up when a new world is built at compile time.

### Queue Information

This section offers a more detailed description of the operations queues that appear in the Agenda Status Bar. There are 3 queues,

- Remote: operations originating on other machines.
- Local: operations originating on the local CYC® image.
- Auxiliary: special queue for use during KB dumps.

broken up into 3 sections, starting at the top:

1. Remote
   - The number of operations from the remote queue that have been read but not yet processed. These operations will not yet have had any effect on the local image.
   - The total number of operations processed by the local CYC® image, regardless of origin. This includes both remote and local operations, regardless of whether they caused an error in the CYC® Agenda.
2. Local
   - The number of operations on the local queue which have yet to be processed. These operations will not yet have had any effect on the local image.
   - The number of operations which have been processed by the local image, but not yet recorded. The changes effected by these operations will be evident in the local image.
   - The number of operations originating in the local CYC® image that have been processed and recorded. Only operations showing up here will be added to the master transcript if processed operations are sent.
3. Auxiliary (will only appear if queue is non-empty)
   - The number of operations from the auxiliary queue that have been processed by the local image.
   - The number of operations from the auxiliary queue that have been read but not yet processed. These operations will not yet have had any effect on the local image.

### Transcript Information

Depending on the communication status, operations processed by a CYC® image may be written out to a special file called a transcript file. For every image, there are two relevant kinds of transcript files:

- Master Transcript: the trancript file common to all CYC® images on a given network. Processed operations which are transmitted are added to this file. Operations received from others are read from this file.
- Local Transcript: the transcript file specifically for the local image.to which the CYC® Agenda is writing operations. If the Agenda is storing operations for later, locally originating processed operations will be written to this file. This filename is often the one to use when loading a transcript manually via the "Load Transcript File" link in the CYC® Navigator.

To view the contents of either the Master or Local Transcript, simply click on the highlighted name. A word of caution: the master transcript can get a bit long, and so may take some time to load.

Below the name of the Master Transcript, the number of characters and estimated number of operations in the transcript are displayed. The actual number of operations read is listed as well.

Below the name of the Local Transcript, the number of operations in the file is listed.

If either transcript has 0 operations, it is empty.

### Historical Information

At the bottom of the System Area, a summary of queue/transcript information is presented:

- Total number of operations from the remote queue that were processed by the local image.
- Total number of operations from the local queue that were processed by the local image.
- Total number of operation that originated in the local image that were sent to the Master Transcript.
- Total number of operations from the auxiliary queue that were processed by the local image.

For details on communication status settings and transcript files, see the CYC® Agenda and Transcripts Documentation.

Go to Top