Re: [Communicator-user] Festival/Unit Tester

[<ne...@ca...>]

Sam and Alan,
Sorry it's taken me so long to respond -- we're in the middle of midterms
right now.  Anyway, here's the full output of the unit tester:

[exec /usr/bin/python
/usr/local/GalaxyCommunicator/GalaxyCommunicator-4.0/contrib/MITRE/tools/src/unit_test/unit_tester.py
--as_hub  localhost 1314 2>&1]
======================================

And the festival server:
                                                                                
[exec /Accounts/courses/dialogue/Festival/festival/bin/festival --server
server.scm 2>&1]
server    Mon Oct 20 12:26:58 2003 : Festival server started on port 1314
client(1) Mon Oct 20 12:27:00 2003 : accepted from localhost.localdomain
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : handshake
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : :conn_type
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
SIOD ERROR: unbound variable : 
client(1) Mon Oct 20 12:27:06 2003 : disconnected
======================================

(This is after starting first the festival server, then the unit tester,
then stopping the unit tester.)

As far as the program file goes, I'm a little confused. As far as I 
can tell, there's no place to specify the program file when starting the
unit tester as the hub.  Please let me know if I'm wrong about this.

And finally, do you know where I can find info on what kinds of frames the
festival server needs to send and receive?  I've been digging for awhile
with no luck.

Thanks,
Kate

On Thu, 16 Oct 2003, Samuel L. Bayer wrote:

> 
>     ne...@ca... writes on 16 October 2003:
>     > Hello folks --
>     > 
>     > I'm using communicator for my senior thesis project (a dialogue system for
>     > registering for classes), and I'm having some troubles with getting it to
>     > talk to Festival correctly.
>     > I can run Festival in command-line mode (as a server or not) without any
>     > problems, and I can launch the process monitor with the unit tester and
>     > Festival as a server.  I can then start the Festival server, but once I
>     > start the Unit Tester, I get a long list of "SIOD error: unbound variable"
>     > statements in the Festival window.  A couple of them are followed by
>     > "handshake" or ":conn_type", but most don't say what variable they're
>     > referring to.
> 
>    I'm not sure I can help with the communicator usage, though might,
>    but if you send me the the start of the SIOD errors: you
>    are getting I might be able to help narrow this down.
> 
> Send it to both Alan and me. I'd want to see a dump of both the unit
> tester and the festival server. 
> 
> Oh, actually, I already know what the problem is. I'm almost positive
> that the problem is that the unit tester doesn't do brokering. This
> isn't documented anywhere, I now realize - I simply forgot to mention
> it, for which I apologize. I'm not sure how precisely the problem is
> manifesting itself, but if you send me the Hub program file you're
> using it'll probably be obvious to me immediately. 
> 
> Cheers,
> Sam Bayer
> 
> 
>