returnNullHypotheses when runRecognitionOnWavFileAtPath – Politepix /forums/topic/returnnullhypotheses-when-runrecognitiononwavfileatpath/feed/ Tue, 23 Apr 2024 15:03:31 +0000 https://bbpress.org/?v=2.6.9 en-US /forums/topic/returnnullhypotheses-when-runrecognitiononwavfileatpath/#post-1021314 <![CDATA[returnNullHypotheses when runRecognitionOnWavFileAtPath]]> /forums/topic/returnnullhypotheses-when-runrecognitiononwavfileatpath/#post-1021314 Mon, 19 May 2014 09:40:00 +0000 buec Hi,

I have just noticed that the returnNullHypotheses doesn’t work, when running runRecognitionOnWavFileAtPath. I think it would be very useful if you get null hypotheses when trying to test something.

Regards
Matthias

]]> /forums/topic/returnnullhypotheses-when-runrecognitiononwavfileatpath/#post-1021316 <![CDATA[Reply To: returnNullHypotheses when runRecognitionOnWavFileAtPath]]> /forums/topic/returnnullhypotheses-when-runrecognitiononwavfileatpath/#post-1021316 Mon, 19 May 2014 09:53:34 +0000 Halle Winkler Hi Matthias,

Thanks for your feedback. runRecognitionOnWavFileAtPath is deprecated as a method of testing now that there is the much more real-world test approach available by using PocketsphinxController’s pathToTestFile property – among its many benefits is that unlike runRecognitionOnWavFileAtPath it uses the main recognition loop, so as test-affecting features are added (like returnNullHypotheses, smartCMN,) they are automatically supported in testing as well.

]]>