It might be necessary to load the file
lib\german\ims_german_debugtools.scm
explicitly if your version of Festival does not do this automatically
when starting. To load a scheme file just say:
festival> (require 'ims_german_debugtools.scm)
Now everything should be ready to go.
festival> (time_test ``This is a test.'' 100 ``TIMINGS.TXT'')
This creates the file TIMINGS.TXT which will contain some
lines like the following:
Initialize took 0.134 ms
Text took 5.364 ms
Token_POS took 3.900 ms
Token took 1777.319 ms
POS took 0.190 ms
Phrasify took 55.365 ms
Word took 362.162 ms
Pauses took 26.005 ms
Intonation took 161.049 ms
PostLex took 462.426 ms
Duration took 227.876 ms
Int_Targets took 830.978 ms
Wave_Synth took 709.949 ms
Initialize took 0.157 ms
...
Now you may run analyse_timingfile.pl to get a summary of
the contents of TIMINGS.TXT:
ara [/Festival_1.4/lib] : analyse_timingfile.pl
TIMINGS.TXT RESULTS.TXT
This will create the file RESULTS.TXT and show its contents
on screen:
TIMINGS.TXT -> RESULTS.TXT
Number of data sets : 100
Lines per data set : 13
Initialize : 0.147 ms 0.18 %
Text : 0.300 ms 0.36 %
Token_POS : 0.140 ms 0.17 %
Token : 31.126 ms 37.39 %
POS : 0.170 ms 0.20 %
Phrasify : 1.115 ms 1.34 %
Word : 5.380 ms 6.46 %
Pauses : 0.713 ms 0.86 %
Intonation : 1.851 ms 2.22 %
PostLex : 4.472 ms 5.37 %
Duration : 2.910 ms 3.50 %
Int_Targets : 4.044 ms 4.86 %
Wave_Synth : 30.874 ms 37.09 %
-----------------------
If you want to assign the contents of a text file to a variable you
can achieve this by using the function (filecontents_to_string
FILENAME) (also contained in
lib\german\ims_german_debugtools.scm).
festival> (set! longtext (filecontents_to_string
``novel.txt''))