Next: 16 HTK Standard Lattice Format (SLF)
Up: 15 Error and Warning Codes
Previous: 15.1 Generic Errors
- HCOPY
-
- +1030
- Non-existent part of file specified
HCOPY needed to access a non-existent part of the input file.
Check that the times are specified correctly, that the label file
contains enough labels and that it corresponds to the data file.
-
- Label file formatted incorrectly
HCOPY is only able to properly copy label files with the
same number of levels/alternatives. When using labels with multiple
alternatives only the first one is used to determine segment
boundaries.
- +1032
- Appending files of different type/size/rate
Files that are joined together must have the same parameter kind and
sample rate.
- -1089
- ALIEN format set
Input/output format has been set to ALIEN, ensure that
this was intended.
- HLIST
-
- HLED
-
- +1230
- Edit script syntax error
The HLED command script contains a syntax error, check the
input script against the descriptions of each command in
section 13.8 or obtained by running HLEd -Q.
-
- Operation invalid
You have either exceeded HLED limits on the number of
boundaries that can be specified, tried to perform an operation on
a non-existent level or tried to sort an auxiliary level into time
order. None of these operations are supported.
- +1232
- Cannot find pronunciation
The dictionary does not contain a valid pronunciation (only occurs
when attempting expansion from a dictionary).
- -1289
- ALIEN format set
Input/output format has been set to ALIEN, ensure that
this was intended.
- HLSTATS
-
-
- No operation specified
You have invoked HLSTATS but have not specified an operation
to be performed.
- -1389
- ALIEN format set
Input format has been set to ALIEN, ensure that this was
intended.
- HDMAN
-
-
- Limit exceeded
HDMAN has several built in limits on the number of different
pronunciation, phones, contexts and command arguments. This error
occurs when you try to exceed one of them.
-
- Item not found
Could not find item for deletion. Check that it actually occurs in the
dictionary.
-
- Edit script file syntax error
The HDMAN command script contains a syntax error, check the
input script against the descriptions of each command in
section 13.4 or obtained by running HDMan -Q.
-
- Dictionary file syntax error
One of the input dictionaries contained a syntax error. Ensure that
it is in a HTK readable form (see section 11.7).
- HSLAB
-
- -1589
- ALIEN format set
Input/output format has been set to ALIEN, ensure that
this was intended.
- HCOMPV
-
- +2020
- HMM does not appear in HMMSet
Supplied HMM filename does not appear in HMMSet. Check
correspondence between HMM filename and HMMSet.
- +2021
- Not enough data to calculate variance
There are not enough frames of data to evaluate a
reliable estimate of variance. Use more data.
- +2030
- Needs continuous models
HCompV can only operate on models with an HMM set kind
of PLAINHS or SHAREDHS.
- +2050
- Data does not match HMM
An aspect of the data does not match the equivalent aspect in
the HMMSet. Check the parameter kind of the data.
- -2089
- ALIEN format set
Input format has been set to ALIEN, ensure that this was
intended.
- HINIT
-
- +2120
- Unknown update flag
Unknown flag set by -u option, use combinations of
tmvw.
- +2121
- Too little data
Not enough data to reliably estimate parameters. Use more
training data.
- +2122
- Segment with fewer frames than model states
Segment may be too short to be matched to model, do not use
this segment for training.
- +2123
- Cannot mix covariance kind in a single mix
Covariance kind of all mixture components in any one state must be
the same.
- +2124
- Bad covariance kind
Covariance kind of mixture component must be either
FULLC or DIAGC.
- +2125
- No best mix found
The Viterbi mixture component allocation failed to find a most likely
component with this data. Check that data is not corrupt and
that parameter values produced by the initial uniform segmentation
are reasonable.
- +2126
- No path through segment
The Viterbi segmentation failed to find a path through
model with this data. Check that data is not corrupt and that
a valid path exists through the model.
- +2127
- Zero occurrence count
Parameter has had no data assigned to it and cannot be
updated. Ensure that each parameter can be estimated by
using more training data or fewer parameters.
- +2129
- HMM not found
HMM missing from HMMSet. Check that the HMMSet is complete and
has not been corrupted.
- +2150
- Data does not match HMM
An aspect of the data does not match the equivalent aspect in
the HMMSet. Check the parameter kind of the data.
- +2170
- Index out of range
Trying to access a mixture component or VQ index beyond the
range in the current HMM.
- -2189
- ALIEN format set
Input format has been set to ALIEN, ensure that this was
intended.
- HREST
-
- +2220
- Unknown update flag
Unknown flag set by -u option, use combinations of
tmvw.
- +2221
- Too few training examples
There are fewer training examples than the minimum set by the
-m option (default 3). Either reduce the value specified
by -m or use more training examples.
- +2222
- Zero occurrence count
Parameter has had no data assigned to it and cannot be
updated. Ensure that each parameter can be estimated by
using more training data or fewer parameters.
- +2223
- Floor too high
Mix weight floor has been set so high that the sum over all
mixture components exceeds unity. Reduce the floor value.
- -2225
- Defunct Mix X.Y.Z
Not enough training data to re-estimate the covariance vector of
mixture component Z in stream Y of state X. The weight of the mixture
component is set to 0.0 and it will never recover even with further
training.
- +2226
- No training data
None of the supplied training data could be used to
re-estimate the model. Data may be corrupt.
- +2250
- Data does not match HMM
An aspect of the data does not match the equivalent aspect in
the HMMSet. Check the parameter kind of the data.
- -2289
- ALIEN format set
Input format has been set to ALIEN, ensure that this was
intended.
- HEREST
-
- +2320
- Unknown update flag
Unknown flag set by -u option, use combinations of
tmvw.
- +2321
- Unknown model
Model in HMM List not found in HMMSet, check that the
correct HMM List is being used.
- +2322
- Invalid output probability
Mixture component probability has not been set. This should
not occur in normal use.
- +2323
- Beta prune failed on taper
Utterance is possibly too short for minimum duration
of model sequence. Check transcription.
- -2324
- No path through utterance
No path was found on the beta training pass, relax the
pruning threshold.
- +2325
- Empty label file
No labels found in label file, check label file.
- -2326
- No transitions
No transition out of an emitting state, ensure that
there is a transition path from beginning to end of model.
- +2327
- Floor too high
Mix weight floor has been set so high that the sum over all
mixture components exceeds unity. Reduce the floor value.
- +2328
- No mixtures above floor
None of the mixture component weights are greater than the floor value,
reduce the floor value.
- -2330
- Zero occurrence count
Parameter has had no data assigned to it and cannot be
updated. Ensure that each parameter can be estimated by
using more training data or fewer parameters.
- -2331
- Not enough training examples
Model was not updated as there were not enough training examples.
Either reduce the minimum specified by -m or
use more data.
- +2350
- Data does not match HMM
An aspect of the data does not match the equivalent aspect in
the HMMSet. Check the parameter kind of the data.
- -2389
- ALIEN format set
Input format has been set to ALIEN, ensure that this was
intended.
- HSMOOTH
-
- +2420
- Unknown update flag
Unknown flag set by -u option, use combinations of
tmvw.
- +2421
- Invalid HMM set kind
HSMOOTH can only be used if HMM set kind is either
DISCRETE or TIED.
- +2422
- Too many monophones in list
HSMOOTH is limited to HMMSets containing fewer than
500 monophones.
- +2423
- Different number of states for smoothing
Monophones and context-dependent models have differing
numbers of states.
- -2424
- No transitions
No transition out of an emitting state, ensure that
there is a transition path from beginning to end of model.
- +2425
- Floor too high
Mix weight floor has been set so high that the sum over all
mixture components exceeds unity. Reduce the floor value.
- -2427
- Zero occurrence count
Parameter has had no data assigned to it and cannot be
updated. Ensure that each parameter can be estimated by
using more training data or fewer parameters.
- -2428
- Not enough training examples
Model was not updated as there were not enough training examples.
Either reduce the minimum specified by -m or
use more data.
- HQUANT
-
- +2530
- Stream widths invalid
The chosen stream widths are invalid. Check that these match the
parameter kind and are specified correctly.
- +2531
- Data does not match codebook
Ensure that the parameter kind of the data matches that of the codebook
being generated.
- HHED
-
-
- Tying null or different sized items
You have executed a tie command on items which do not have the
appropriate structure or the structures are not matched. Ensure
that the item list refers only to the items that you wish to tie
together.
- -2631
- Performing operation on no items
The item list was empty, no operation is performed.
- +2632
- Command parameter invalid
The parameters to the command are invalid either because they
refer to parts of the model that do not exist (for instance a
state that does not appear in the model) or because they
do not represent an acceptable value (for instance HMMSet kind
is not PLAINHS, SHAREDHS, TIEDHS or
DISCRETEHS).
- +2634
- Join parameters invalid or not set
Make sure than the join parameters (set by the JO command)
are reasonable. In particular take care that the floor is low enough
to ensure that when summed over all the mixture
components the sum is below 1.0.
- +2635
- Cannot find matching item
Search for specified item was unsuccessful. When this occurs with
the CL or MT commands ensure that the appropriate
monophone/biphone models are in the current HMMSet.
- -2637
- Small gConst
A small gConst indicates a very low variance in that particular
Gaussian. This could be indicative of over-training of the models.
- -2638
- No typical state
When tying states together a search is performed for the distribution
with largest variance and all tied states share this distribution. If
this cannot be found the first in the list will be used instead.
- -2639
- Long macro name
In general macro names should not exceed 20 characters in length.
- +2640
- Not implemented
You have asked HHED to perform a function that is not
implemented.
- +2641
- Invalid stream split
The specified number/width of the streams does not agree with the
parameter kind/vector size of the models.
- +2650
- Edit script syntax error
The HHED command script contains a syntax error, check the
input script against the descriptions of each command in
section 13.6 or obtained by running HHEd -Q.
- +2651
- Command range error
The value specified in the command script is out of range. Ensure that
the specified state exists and the the value given is valid.
-
- Stats file load error
Either loading occupation statistics for the second time or executing
an operation that needs the statistics loaded without loading them.
- +2660
- Trees file syntax error
The trees file format did not correspond to that expected. Ensure that
the file is complete and has not been corrupted.
- +2661
- Trees file macro/question not recognised
The question or macro referred to does not exist. Ensure that the file
is complete and has not been corrupted.
- +2662
- Trying to sythesize for unknown model
There is no tree or prototype model for the new context. Ensure that a
tree has been constructed for the base phone.
-
- Invalid types to tree cluster
Tree clustering will only work for single Gaussian untied models of
similar topology.
- HBUILD
-
-
- Mismatch between command line and language model
Ensure that the !ENTER and !EXIT words are correctly
defined and that the supplied files are of the appropriate type.
-
- Unknown word
Ensure that the word list corresponds to the language model/lattice
supplied.
- HPARSE
-
-
- Variable not defined
You have referenced a network that has not yet been defined. Check
that all networks are defined before they are referenced.
-
- Loop or word expansion error
There is either a mismatch between the WD_BEGIN WD_END
pairs or a triphone loop is badly formed.
-
- Dictionary error
When generating a dictionary a word exceeded the maximum number of
phones, a word occurred twice or no dictionary was produced.
-
- Syntax error in HParse file
The HPARSE network definition contains a syntax error, check
the input file against the network description in
section 13.1.
- HVITE
-
-
- Unsupported operation
HVITE is not able to perform the operation requested
-
- Data does not match HMMs
There is a mismatch between the data file and the HMMSet. Ensure that
the data is parameterised in the correct format and the configuration
parameters match those used during training.
- -3289
- ALIEN format set
Input/output format has been set to ALIEN, ensure that
this was intended.
- HRESULTS
-
- -3330
- Empty file
The file was empty and will be skipped.
- +3331
- Unknown label
The label did not appear in the list supplied to HResults.
This error will only occur if calculating confusion matrices so
normally the contents of the word list file will have no effect
on results.
- +3332
- Too many labels
HRESULTS will only generate confusion statistics for a small
number of labels.
-
- Cannot calculate word spot results
When calculating word spotting results the label files need to have
both times and scores present.
- -3389
- ALIEN format set
Input format has been set to ALIEN, ensure that this was
intended.
- HSHELL
-
- +5020
- Command line processing error
- +5021
- Command line argument type error
- +5022
- Command line argument range error
The command line is badly formed. Ensure that it matches the
syntax and values expected by the command (check the manual
page or the syntax obtained by running HTOOL without any
arguments).
- +5050
- Configuration file format error
HSHELL was unable to parse the configuration. Check that
it is of the format described in section 4.3.
- +5051
- Script file format error
Check that the script file is just a list of file names and that
if any file names are quoted that the quotes occur in pairs.
- +5070
- Module version syntax error
A module registered with HShell with an incorrectly formatted
version string (which should be of the form
"!HVER!HModule: Vers.str [WHO DD/MM/YY]").
- +5071
- Too many configuration parameters
The size of the buffer used by one of the tools or modules to read
its configuration parameters was exceeded. Either reduce the total
number of configuration parameters in the file or make more of then
specific to their particular module rather than global.
- +5072
- Configuration parameter of wrong type
The configuration parameter is of the wrong type. Check that its type
agrees with that shown in chapter 14.
- +5073
- Configuration parameter out of range
The configuration parameter is out of range.
- HMEM
-
- +5170
- Heap parameters invalid
You have tried to create a heap with unreasonable parameters. Adjust
these so that the growth factor is positive and the initial block
size is no larger than the maximum. For MSTAK the element
size should be 1.
- +5171
- Heap not found
The specified heap could not be found, ensure that it has not been
deleted or memory overwritten.
- +5172
- Heap does not support operation
The heap is of the wrong type to support the requested operation. In
particular it is not possible to Reset or Delete a
CHEAP.
- +5173
- Wrong element size for MHEAP
You have tried to allocate an item of the wrong size from a
MHEAP. All items on a MHEAP must be of the same size.
- +5174
- Heap not initialised
You have tried to allocate an item on a heap that has not yet been
created. Ensure that CreateHeap is called to initialise
the heap before any items are allocated from it.
- +5175
- Freeing unseen item
You have tried to free an item from the wrong heap. This can occur
if the wrong heap is specified, the item pointer has been corrupted
or the item has already been freed implicitly by a
Reset/DeleteHeap call.
- HMATH
-
- +5220
- Singular covariance matrix
The covariance matrix was not invertible. This may indicate a lack
of training data or linearly dependent parameters.
- +5270
- Size mismatch
The input parameters were of incompatible sizes.
- +5271
- Log of negative
Result would be logarithm of a negative number.
- HSIGP
-
- +5320
- No results for WaveToLPC
Call did not include Vectors for the results.
- +5321
- Vector size mismatch
Input vectors were of mismatched sizes.
- -5322
- Clamped samples during zero mean
During a zero mean operation samples were clipped as they were outside
the allowable range.
- HAUDIO
-
- +6020
- Replay buffer not active
Attempt to access a replay buffer when one was not attached.
- +6021
- Cannot StartAudio without measuring silence
An attempt was made to start audio input through the silence detector
without first measuring or supplying the background silence values.
- +6070
- Audio frame size/rate invalid
The choice of frame period and window duration are invalid. Check
both these and the sample rate.
- -6071
- Setting speech threshold below silence
The thresholds used in the speech detector have been set so that the
threshold for detecting speech is set below that of detecting silence.
- HVQ
-
- +6150
- VQ file format error
The VQ file was incorrectly formatted. Ensure that the file is
complete and has not been corrupted.
- +6151
- VQ file range error
A value from the VQ file was out of range. Ensure that the file is
complete and has not been corrupted.
- +6170
- Magic number mismatch
The VQ magic number (normally based on parameter kind) does not match
that expected. Check that the parameter kind used to quantise the data
and create the VQ table matches the current parameter kind.
- +6171
- VQ table already exists
All VQ tables must have distinct names. This error will occur if you
try to create or load a VQ table with the same name as one already
loaded.
- +6172
- Invalid covariance kind
Entries in VQ tables must have either NULLC, FULLC or
INVDIAGC covariance kind.
- +6173
- Node not in table
A node was missing from the VQ table. Ensure that the VQ table was
properly created or that the file was complete.
- +6174
- Stream codebook mismatch
The number or size of streams in the VQ table does not match that
requested.
- HWAVE
-
- +6220
- Cannot fseek/ftell
Unless the wave file is read through a pipe fseek and ftell are
expected to work correctly so that HWAVE can calculate the
file size. If this error occurs when using an input pipe, supply
the number of samples in the file using the configuration variable
NSAMPLES.
- +6221
- File appears to be a infinite
HWAVE cannot determine the size of the file.
- +6230
- Config parameter not set
A necessary configuration parameter has not been set. Determine the
correct value and place this in the configuration file before
re-invoking the tool.
- +6250
- Premature end of header
HWAVE could not read the complete file header.
- +6251
- Header contains invalid data
HWAVE was unable to successfully parse the header. The header
is invalid, of the wrong type or be a variation that HWAVE does
not handle.
- +6252
- Header missing essential data
The header was missing a piece of information necessary for
HWAVE to load the file. Check the processing of the
input file and re-process if necessary.
- +6253
- Premature end of data
The file ended before all the data was read correctly. Check that the
file is complete, has not been corrupted and where necessary
NSAMPLES is set correctly.
- +6254
- Data formated incorrectly
The data could not be decoded properly. Check that the file was
complete and processed correctly.
- +6270
- File format invalid
The file format is not valid for the operation requested.
- +6271
- Attempt to read outside file
You have tried to read a sample outside of the waveform file.
- HPARM
-
- +6320
- Configuration mismatch
The data file does not match the configuration. Check the
configuration file is correct.
- +6321
- Invalid parameter kind
Parameter kind is not valid. Check the configuration file.
- +6322
- Conversion not possible
The specified conversion is not possible. Check the configuration is
correct and re-code the data from waveform files if necessary.
- +6323
- Audio error
An audio error has been detected. Check the HAUDIO
configuration and the audio device.
- +6324
- Buffer not initialised
Ensure that the buffer is used in the correct manner.
- +6350
- CRC error
The CRC does not match that of the data. Check the data file is
complete and has not been corrupted.
- -6351
- Byte swapping not possible
HPARM will attempt to byte swap parameter files but this
may not work if the floating point representation of the machine
that generated the file is different from that which is reading it.
- +6352
- File too short to parameterise
The file does not contain enough data to produce a single observation.
Check the file is complete and not corrupt. If it is, it should be
discarded.
- +6370
- Unknown parameter kind
The specified parameter kind is not recognised. Refer to
section 5.15 for a list of allowable parameter kinds
and qualifiers.
- +6371
- Invalid parameters for coding
The chosen parameters are not valid for coding. Choose different ones.
- +6372
- Stream widths not valid
Cannot split the data into the specified number of streams. Check that
the parameter kind is correct and matches any models used.
- +6373
- Buffer/observation mismatch
The observation parameter kind should match that of the input buffer.
Check that the configuration parameter kind is correct and matches
that of any models used.
- +6374
- Buffer size too small for window
Calculation of delta parameters requires a window larger than the
buffer size chosen. Increase the size of the buffer.
- +6375
- Frame not in buffer
An attempt was made to access a frame that does not appear in the
buffer. Make sure that the file actually contains the specified frame.
- HLABEL
-
- +6520
- MLF index out of range
An attempt was made to access an MLF that has not been loaded or to
load too many MLFs.
- +6521
- fseek/ftell not possible
HLABEL needs random access to MLFs. This error is generated
when this is not possible (for instance if access is via a pipe).
- +6550
- HTK format error
- +6551
- MLF format error
- +6552
- TIMIT format error
-
- ESPS format error
- +6554
- SCRIBE format error
A label file was formatted incorrectly. Label
file formats are described in chapter 6.
- +6570
- Level out of range
Attempted to access a non-existent label level. Check that the correct
label file has been loaded.
- +6571
- Label out of range
Attempted to access a non-existent label. Check that the correct
label file has been loaded and that the correct level is being
accessed.
- +6572
- Invalid format
The specified file format is not valid for the particular operation.
- HMODEL
-
- +7020
- Cannot find physical HMM
No physical HMM exists for a particular logical model. Check that the
HMMSet was loaded or created correctly.
- +7021
- INVDIAG internal format
Attempts to load or save models with INVDIAG covariance kind
will fail as this is a purely internal model format.
-
- varFloor should be variance floor
HMODEL reserves the macro name varFloorN as the
variance floor for stream N. These should be variance
macros (type v) of the correct size for the particular stream.
- +7024
- Variance tending to 0.0
A variance has become too low. Start using a variance floor or
increase the amount of training data.
- +7030
- HMM set incomplete or inconsistent
The HMMSet contained missing or inconsistent data. Check that the
file is complete and has not been corrupted.
- +7031
- HMM parameters inconsistent
Some model parameters were inconsistent. Check that the file is
complete and has not been corrupted.
-
- Option mismatch
All HMMs in a particular set must have consistent options.
- +7035
- Unknown macro
Macro does not exist. Check that the name is correct and appears
in the HMMSet.
- +7036
- Duplicate macro
Attempted to create a macro with the same name as one already present.
Choose a different name.
- +7037
- Invalid macro
Macro had invalid type. See section 7.3 describes the
allowable macro types.
- +7050
- Model file format error
- +7060
- HMM List format error
The file was formated incorrectly. Check the file is complete and
has not been corrupted.
- +7070
- Invalid HMM kind
Invalid HMMSet kind. Check that this is specified correctly.
- +7071
- Observation not compatible with HMMSet
Attempted to calculate an observation likelihood for an observation
not compatible with the HMMSet. Check that the parameter kind is
set correctly.
- HTRAIN
-
- +7120
- Clustering failed
Almost certainly due to a lack of data, reduce the
number of clusters requested or increase amount of data.
- +7150
- Accumulator file format error
Cannot read an item from an accumulator file. Check
that file is complete and not corrupted.
- +7170
- Unsupported covariance kind
Covariance kind must be either FULLC, DIAGC or
INVDIAGC.
- +7171
- Item out of range
Attempt made to access data beyond expected range. Check that
the item number is correct.
- +7172
- Tree size must be power of 2
Requested codebook size must be a power of 2 when
using tree based clustering.
- -7173
- Segment empty
Empty data segment in file. Check that file has not
become corrupted and that the start and end segment times
are correct.
- HUTIL
-
- +7220
- HMMSet empty
A scan was initiated for a HMMSet with no members.
- +7230
- Item list parse error
The item list syntax was incorrect. Check the item list specification
in section 13.6.
- +7231
- Item list type error
Each item in a particular list should be of the same type and size.
- +7250
- Stats file format error
Stats file is of wrong format. Note the format of the stats file has
changed in HTK_V2.0 and old files will need converting to the new
format.
- +7251
- Stats file model error
A model name encountered in the stats file is invalid check that the
model set corresponds to that used to generate the stats file and that
the stats file is complete and has not been corrupted.
- +7270
- Accessing non-existent macro
Attempt to perform operation on non-existent macro.
- +7271
- Member id out of range
Attempt to perform set operation on out of range member.
- HDICT
-
- +8050
- Dictionary file format error
The dictionary file is not correctly formatted.
Section 11.7 describes the HTK dictionary file format.
- HLM
-
- +8150
- LM syntax error
The language model file was formatted incorrectly. Check the file is
complete and has not been corrupted.
-
- LM range error
The specified value(s) for the language model probability are not
valid. Check the input files are correct.
- HNET
-
- +8220
- No such word
The specified word does not exist or does not have a valid
pronunciation.
- +8230
- Contexts not consistent
HNET can only deal with the standard HTK method for specifying
context left-phone+right and will only allow context free
phones if they are context independent and only form part of the word.
- +8231
- No such model
A particular model could not be found. Make sure that the network is
being expanded in the correct fashion and then ensure that your HMM
list will cover all required contexts.
- +8232
- Lattice badly formed
Could not convert lattice to network. The lattice should have a single
well defined start and a single well defined end. When cross word
expansion is being performed the number of !NULL words that
can be concatenated in a string is limited.
- +8250
- Lattice format error
The lattice file is formatted incorrectly. Ensure that the lattice
is of the format described in chapter 16.
- +8251
- Lattice file data error
The value specified in the lattice file is invalid.
- +8252
- Lattice file with multiple start/end nodes
A lattice should have only one well defined start node and one
well defined end node.
- HREC
-
-
- Invalid HMM
One of the HMMs in the network is invalid. Check that the HMMSet
has been correctly initialised.
- +8521
- Network structure invalid
The network is incorrectly structured. Take care to avoid loops
that can be traversed without consuming observations (this may occur
if you introduce any 'tee' words in which all the models making up that
word contain tee-transitions). Also ensure that the recogniser and
the network have been created and initialised correctly.
- +8522
- Lattice structure invalid
The lattice was incorrectly formed. Ensure that the lattice was
created properly.
-
- Recogniser not initialised correctly
Ensure the recogniser is initialised and used correctly.
- +8571
- Data does not match HMMs
The observation does not match the HMM structure. Check the parameter
kind of the data and ensure that the data is matched to the HMMs.
- HGRAF
-
- +6870
- X11 error
Ensure that the DISPLAY variable is set and that the
X11 window system is configured correctly.
Next: 16 HTK Standard Lattice Format (SLF)
Up: 15 Error and Warning Codes
Previous: 15.1 Generic Errors
ECRL HTK_V2.1: email [email protected]