These options affect the behavior of CTAT generally.
Enables communication with a natural language system.
Invokes the computer's default browser whenever the student traverses a link marked with a URL in the Attach Dialogue dialog. The URL is formed by combining the External URL for Link Traversal (defined below) and link-specific data.
The base URL used for links that specify invoking a web browser. This URL is only valid if the Invoke Browser on External URL option is turned on.
If enabled, logging messages will be sent to server whose URL is defined in the preference Logging Server URL (below).
URL of the logging server. For PSLC experiments, this is typically a LearnLab server.
If enabled, logging messages will be stored in text
files on the local hard disk of the machine running the tutor.
The location for storing these files is determined by the
Disk Logging Directory preference. If the
Use Login Window preference is enabled,
disk logs will be named using the student's username as the
first part of the file name; otherwise, the system log-in name
will be used in the file name.
A path for the directory in which disk logging files
will be stored. This item is only valid if Log to Disk is
enabled. For relative paths, the path is relative to the
parent of the folder from which the current student interface
was loaded. For example, if the student interface is in
{CTAT}/Projects/Interface, the specified path is
relative to {CTAT}/Projects. To log to this
folder, use '.' (without quotes).
If enabled, a CTAT log-in window will be presented to
the student before they can use the tutor. The log-in window
prompts for a username and password for the purposes of
logging, though only username is required. Neither username or
password is authenticated. Using the log-in window in
combination with the Log to Disk preference
ensures that the student-entered username will be used in the
file name of the log file.
The default top-level folder for files created while authoring. If this preference is not set, the Problems Organizer will not be used in Save and Open dialogs. Relative paths are relative to the folder from which the current student interface was loaded. If the value is empty or no interface is loaded, the location is relative to the current working directory.
The default location for CTAT to check for cognitive model files. Unless explicitly set, this folder is set to the folder from which the current Java student interface was loaded, or the folder from which the last behavior graph was loaded.
Behavior graph preferences are default options to be used for new behavior graphs. To change these preferences for a single graph, see Section 5.1, “Behavior Graph Options”
If enabled, student input during tutoring must match the case of the input recorded in the graph for the input to be considered correct. This setting applies to Exact Matches only; other types of input matching (e.g., wildcard, regular expression) are not affected.
If enabled, no feedback is given to the student during tutoring. This feature is commonly used for online testing.
If enabled, the top-level group of the behavior graph is 'unordered'. In a graph with no other ordering constraints (ie, groups), this means that a student can perform the actions recorded in the graph in any order; otherwise the actions must be performed in the order shown in the graph, from start state to done state. See Section 3.2.3, “Ordering Constraints” for more information.
If enabled, a student's correct input to a widget will lock that widget. Otherwise, the student is able to change a widget's value after a correct answer. Enabled by default.
If enabled, a message such as “Please work on the highlighted step” will be shown to the student when the student interacts with a widget not specified on the next correct action link in the graph. Disabling this feature may be useful in cases where highlighting the correct widget gives away the answer (eg, when the correct widget is a button). For unordered steps, the next correct action link is the next link within the current unordered group that is both preferred and untraversed.
These options affect the behavior of CTAT's Behavior Recorder.
If enabled, dragging one node in the graph will drag all child nodes; otherwise, only the one node will move.
If enabled, links in the graph can be designated as preferred, customizing the preferred problem-solving path. Enabled by default.
If enabled, the Behavior Recorder will count link traversals in demonstrate mode, and display them in the graph.
While demonstrating an alternate path, you may demonstrate a step that matches If enabled, the Behavior Recorder will never prompt you about whether or not to link states when it detects that the current state of the student interface matches an existing state in the behavior graph; instead, the Behavior Recorder will always link the similar states. If this preference is disabled, the Behavior Recorder will always ask whether to link to a similar existing state, or to create a new state.
If enabled, you can define links in the graph that the tutor will perform (see Section 3.2.2, “Student- and Tool-Performed Actions”). Enabled by default.
These preferences specify whether or not Eclipse should be used for production rule editing and if so, how CTAT should connect to it.
If enabled, a new menu item, Open Jess File, will appear in the CTAT File menu; and clicking this menu item will prompt CTAT to communicate with plugins in the Eclipse IDE for editing files containing Jess production rules, templates, or facts.
The listening port of the Eclipse IDE plugin for communicating with CTAT. Default port is 6060.
The listening port of CTAT for communicating with the Eclipse plugin. Default port is 6161.
These preferences affect the Jess Console for Cognitive Tutors (Jess).
Turns on chaining in the Jess Console.
Turns on Firable options in the Jess Console.
Break when an exception occurs in the Jess Console.
These preferences affect the Conflict Tree for Cognitive Tutors (Jess).
The maximum number of times a rule can be chained to another. Default number is 5.
The maximum number of bug rules displayed in the Conflict Tree. Default number is 4.
If enabled, the production system will interpret salience defined in production rules. See the Jess Wiki page on salience usage tips for more information.