12 October 1997 Saint-Genest-Malifaux FRANCE lchase@serveur.dtr.fr This is a short set of instructions for unpacking the Visual Error Region Analysis toolkit (also known as the CMU Error Analysis Toolkit) from the gzip'd file era.tar.gz which can be downloaded from the web page http://www.cs.cmu.edu/afs/cs/user/lindaq/mosaic/my-home-page.html ---//------- Here's what you need to do to unpack and install the toolkit at your site: 1. Make sure you have Tk/wish (compatibility with version 4.1 has been tested) installed at your site for your target platform(s). 2. Make sure you have a gcc compiler available for your target platform(s). 3. Download the file era.tar.gz from the above site. It's a tiny bit over 2 megabytes in size. 4. gunzip era.tar.gz to get the uncompressed file era.tar, which is just under 6.4 megabytes in size. 5. Make the home directory for VisERA somewhere convenient, for example /home//ERA and then mv the era.tar file into that directory, and then cd to the same. 6. In the new directory tar xvf era.tar to unpack the following directories: bin doc programs scripts ctl input run 7. cd into programs/visera and type make visera to compile the visera program for your platform. (You will probably need to delete the current file "visera" and all "*.o" files first in order to have the program really recompile. This depends on how your local system timestamps files. I suggest you do this no matter what.) You should have no problems compiling the individual files in this directory. If you do, take a look at the Makefile. If it has more in it than this: # makefile - pour le programme de VisERA (Visual Error Region Analysis) # CC = gcc -g visera: main.o era.o align.o strcasecmp.o salloc.o CM_funcs.o $(CC) -o visera main.o era.o align.o strcasecmp.o salloc.o CM_funcs.o \ -lm .c.o: $(CC) -Iinclude -c -o $@ $*.c then delete everything else and try running make again. If you still have problems, chances are there's a problem with your installation of gcc. Some users have encountered problems with the linking step of the compilation process. If you have the same problem, try editing the Makefile line for visera to refer only to the library "lm" (-lm) instead of the four default libraries (-X11, -tk, -tcl). The program should link without trouble, and should also run without trouble on the test cases (see below). 8. add a directory to ERA/bin for your type of platform. The only entry in the default distribution version is ERA/bin/alpha. If you're on a DEC alpha then go ahead and use this. Otherwise add another, such as mkdir /home//ERA/bin/linux Copy the new binary of "visera" to this directory: cp visera /home//ERA/bin/linux 9. repeat the compile and copy process for the second program in the package, viseraP: cv /home/lindaq/ERA/programs/viseraP make viseraP cp viseraP /home//ERA/bin/linux ---//------- To test the system you'll need to do a few things: 1. You must make some minor adjustments to the default setup. cd into the directory "run": cd /home//ERA/run Here you'll find (among other things) three files that give example command-line calls to the "visera" and "viseraP" programs. NAB.command.line.visera -- word level analysis on male speakers from the North American Business news corpus (CMU's Sphinx-II recognizer output) NAB.command.line.viseraP -- word and phone level analysis on the same data SWB.command.line.visera -- word level analysis on speakers from the Switchboard conversational telephone speech corpus (commercial HTK recognizer output) The contents of the first of these files: $ more NAB.command.line.visera ../scripts/visera.csh ../bin/alpha/visera 0 0 1 ../ctl/h1_dt_94-m.visera.ctl era_in You can see here that the program visera is passed as an argument to a the control script "visera.csh", which is located in the "scripts" directory parallel to the current directory. When used as an argument to this scripte, the program visera is referred to by via an explicit path name -- you should substitute here your new bin directory's location (for instance ../bin/linux/visera). Depending on your system's setup, you may need to substitute the call to "/bin/csh" with "/bin/csh -f" in the first line of the scripts in this directory. The script "visera.csh" also refers to a control file in the parallel directory "ctl". This control file contains a list of test utterances to be examined (in this case the file is /home//ERA/ctl/h1_dt_94-m.visera.ctl You'll need to edit the path names of the files in this control file to match the current installation. In the default distribution the path names are something like /net/alf24/usr0/lindaq/thesis/era/ which in our example should be changed to /home//ERA/ Repeat this renaming process for all control files in the directory "ctl". 2. Now you must make sure your installed version of wish is being pointed to by the visera and viseraP scripts. to find out where your wish resides: which wish The default distribution assumes that wish is in /usr/local/bin/wish If this is not the case, you must edit the first line of each of these files (in directory "run") header.tk headerP.tk printheader.tk printheaderP.tk to reflect wish's actual location. 3. Now you can run the system and see many examples of how it works on the test cases included in the distrubution by executing a command line call such as the examples given in the files. NAB.command.line.visera NAB.command.line.viseraP SWB.command.line.visera a. If you are running on a desktop machine, the window sizes and colors should appear appropriate. If you're running on a laptop machine, you will probably want to play with the following parameters to get more appropriately proportioned windows: In header.tk, headerP.tk, etc: dispwd errdispht parameters -- see the files *.tk for suggested parameter settings. b. Depending on your installation of tk/wish, you may need to edit the scripts in the "scripts" directory (such as visera.csh) to either execute the file "foo.tk" directly or as an argument to wish: # foo.tk wish ./foo.tk in visera.csh ---//------- At this point everything should be running smoothly. You probably didn't have to do very many of the above-mentioned twiddles -- this is a summary of all the little problems various users have found when testing the system... ---//------- Complete documentation of the features of this toolkit, the motivation behind its development, and detailed discussion of examples of its use are given in chapters 4 and 9 of the document "thesis" included in the "doc" directory. That directory also contains detailed input file specifications for the two main programs (visera and viseraP). This help file covers all problems encountered by the twenty or so sites who have installed the toolkit to date. Please send further inquiries, comments, and bug reports to: Lin Chase chase@limsi.fr lchase@serveur.dtr.fr chase@cs.cmu.edu (all three addresses work as of 12 October 1997)