Scripts

Although the framework_code repository is not linked to any particular application, users can still run the integrated system, with the only "action" being the Problem Solver printing out n-tuples.

System Requirements

• Python (versions 2.7 and up should work)
• Pyre, port of Lyre: unzip ecg-package.tar.gz and follow the instructions in INSTALL
• Jython
• ecg-grammars
  • Note: the analyzer.sh script assumes this is installed in the same directory as framework_code
• Six

Note: Once you clone the repository, you'll also want to set your PYTHONPATH in your bash_profile to point to:

{INSTALL_PATH}/framework_code/src/main

Initializing the Analyzer

The ECG Analyzer can be run with Python via Jython. The analyzer.sh script runs the Analyzer using, by default, the research grammar.

Bash:
sh analyzer.sh
OR
./analyzer.sh

If all goes well, you should see the following lines on Terminal:

Jython {information about your Jython installation)
[Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation)]
Analyzer ready...

Visualizing N-tuples

If you're only interested in visualizing n-tuples, and not performing a "smoke test" of the system's end-to-end communication, you can run a debugging tool called the N-tuple Visualizer. Once the ECG Analyzer is running, open up a new Terminal tab in the same directory, then run:

./ntuples.sh

This runs the CoreSpecializer and a proxy of the Analyzer, which communicates with the Jython Analyzer via a local server. You can visualize n-tuples for sentence fragments or whole sentences:

> the box
{givenness: uniquelyIdentifiable
number: singular
type: box}

Try out different sentences, like John saw the box or John pushed the box into the room. If the Analyzer is unable to parse the utterance, you'll get an error resembling the following:

<Fault: No parse found for: 'John created the box into the room'>

End-to-End System

To run the entire end-to-end system (the UI-Agent and the Problem Solver), use the following command:

./setup.sh

This will input language to the UI-Agent, which outputs an n-tuple produced by the Specializer (as seen above). If the intent or "mood" of the n-tuple is identified (command, assertion, query, etc.), it is sent to the Problem Solver using the communication modules. The CoreProblemSolver then prints out the key features of the n-tuple.