issue in generating Language model

Home Forums OpenEars issue in generating Language model

Tagged: ,

Viewing 3 posts - 1 through 3 (of 3 total)

  • Author
    Posts
  • #1030580
    jagdish
    Participant

    Using code from https://www.politepix.com/openears/tutorial/

    And receive errors like below in many words.

    My sample words array to generate model,

    NSArray *words = [NSArray arrayWithObjects:@"WORD", @"STATEMENT", @"OTHER WORD", @"A PHRASE", @"CREATE WORKPLAN",@"BACKWARD", @"CHANGE", @"FORWARD", @"GO", @"LEFT", @"MODEL", @"RIGHT", @"TURN", @"MY APP", @"COMPANY ONE", @"MY COMPANY", @"HELLO WORLD", @"WOKRPLAN", @"TESTING", @"CROSS ROAD", @"PHONE", @"ANKUR CROSS", nil];

    2016-06-09 12:48:41.035 DemoSpeech[222:10462] The word WORKPLAN was not found in the dictionary of the acoustic model /private/var/mobile/Containers/Bundle/Application/2DA9C7A9-14DF-4E10-8190-445667FF7831/DemoSpeech.app/AcousticModelEnglish.bundle. Now using the fallback method to look it up. If this is happening more frequently than you would expect, likely causes can be that you are entering words in another language from the one you are recognizing, or that there are symbols (including numbers) that need to be spelled out or cleaned up, or you are using your own acoustic model and there is an issue with either its phonetic dictionary or it lacks a g2p file. Please get in touch at the forums for assistance with the last two possible issues.

    #1030582
    Halle Winkler
    Politepix

    Welcome,

    Those aren’t errors, they are just notifications that the word wasn’t found in the default lookup dictionary. Jargon like “workplan” or words from other languages such as “Ankur” will be processed using the fallback method because they won’t be found in the default phonetic lookup dictionary – that is expected and it is referenced in the warning. If you are experiencing this with words like “left” or “company” please check out the post Please read before you post – how to troubleshoot and provide logging info here so you can see how to turn on and share the logging that provides troubleshooting information for this kind of issue.

    #1030583
    Halle Winkler
    Politepix

    Logging output was presumably added to your project or the sample app at some point, but if your issue is that you just want to see less of it, you can comment out the line [OELogging startOpenEarsLogging] and/or any references to verbosePocketsphinx. Make sure to turn it back on if you have any issues you want to troubleshoot.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.