In the original MIT Galaxy configuration, the batchmode server takes the place of audio + recognition, and serves a sequence of utterances to the "rec" program. The three servers here (C shell, Python shell, and Python/Tk GUI) all perform the same function interactively, using the MITRE Galaxy stdin polling utility. The C executable is called c_ui; the Python shell executable is py_ui, and the Python/Tk executable is py_gui_ui.
#define DefaultPrompt "Type a sentence: "This server also accepts the standard server arguments. See the command-line argument parsing library in the Galaxy Communicator documentation for details.
#define DefaultProgram "rec"static char *OAS[] = {
"-prompt <str>", "use this prompt", DefaultPrompt,
"-prog_name <name>", "name of program to send messages to", DefaultProgram,
NULL
};
reinitialize
prints a greeting, if present. This is the primary way in which thiese
servers differ from the batchmode server.
| parameter | type | optional | depends on | description/constraints | |
| IN: | :greeting | string | yes | greeting from Hub |
enable_input
delivers output to the UI server and enables input for the next utterance.
In addition to handling string output, it's also possible to pass a random
Gal_Object to this dispatch function for presentation. This server can
thus be used to debug (or collect data for) arbitrary interactions with
the Hub which begin with an input string.
| parameter | type | optional | depends on | description/constraints | |
| IN: | :paraphrase_string | string | yes | paraphrase of last question | |
| :reply_string | string | yes | answer to last question | ||
| :object | unrestricted | yes | object to be printed out | ||
| :utterance_id | integer | yes | utterance index to start at |
This message returns a frame.
{c <program_name>This is virtually identical to the input provided by the batchmode server, and is compatible with other MIT program files. The program name is "rec" by default, but can be modified with the -prog_name command line argument.
:mode "typed"
:utterance_id <integer>
:input_string <string>
:hyp_id 0
}