Problem with **fwdflat ** mode, wrong number of frames
Number of frames as shown in n-best file is not the same as number of frames
in decodelog. Decode-log version is correct.
For example, for file F13MH02A0118I411 nbest list shows 755 frames while
decode_log shows 188 frames
FWDXCT: F13MH02A0118I411 S -1953087 T -4148068 A -4119218 L -28850 0 221969 808 10 -1480076 -20054 saraasarii(2) 76 -1782491 -476 baqgaalii 148 -405385 -7676 +horn+ 155 -405977 -1224 canxe 178 -267258 -228 188
When fwdtree mode is used this problem is not observed.
The hypothesis with "best" score in nbest list is not the one which is shown in decode_log.
Could you please confirm whether the 2nd problem is actually a problem
(best T score hypothesis in nbest list != decoder hyp) or not? i.e. is it
theoretically possible for them to be different (with same params)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think it's a problem. There are insertion penalties and fillers
handled differently during decoder and dag search to generate n-best after
that. The details depend on the type of search you are using though, is it TST
search or something else.
It might be debugged
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
We've observed 2 problems with nbest list that is created in sphinx3. Please
find this zip (http://home.iitb.ac.in/~pranavj/nbest_problems.zip) which contains trimmed log file
, two n-best files
.
Problem with **fwdflat ** mode, wrong number of frames
Number of frames as shown in n-best file is not the same as number of frames
in decodelog. Decode-log version is correct.
For example, for file F13MH02A0118I411 nbest list shows 755 frames while
decode_log shows 188 frames
FWDXCT: F13MH02A0118I411 S -1953087 T -4148068 A -4119218 L -28850 0 221969 808
10 -1480076 -20054 saraasarii(2) 76 -1782491 -476 baqgaalii 148 -405385 -7676 +horn+ 155 -405977 -1224 canxe 178 -267258 -228188When fwdtree mode is used this problem is not observed.
For the file F13MH04A0303I309
decode_log shows
Top-line in nbest list matches with decode_log, but the line with best T score
is third one in n-best list
For file F13MH02A0118I411
decode_log shows
The above matches with second line in n-best list (which is also the line with
best T score).
Could you please explain ambiguity in o/p of n-best list?
Thanks.
Could you please confirm whether the 2nd problem is actually a problem
(best T score hypothesis in nbest list != decoder hyp) or not? i.e. is it
theoretically possible for them to be different (with same params)?
I don't think it's a problem. There are insertion penalties and fillers
handled differently during decoder and dag search to generate n-best after
that. The details depend on the type of search you are using though, is it TST
search or something else.
It might be debugged