- This topic has 9 replies, 2 voices, and was last updated 8 years, 4 months ago by .
-
Posts
-
I had no problems implementing RapidEars with the simple test array from the OpenEars demo. I can not seem to now add RuleORama to the mix. I am not clear on what method I should use to start up the pocketsphinxController. For OpenEars we used startListeningWithLanguageModelAtPath: and with RapidEars we moved to startRealtimeListeningWithLanguageModelAtPath: and in the documentation for RuleORama it moves back to startListeningWithLanguageModelAtPath: so which should we be using for the combo. When I tried building my rule dict with generateFastGrammarFromDictionary: and loading up pocketsphinxController with startRealtimeListeningWithLanguageModelAtPath: it does not seem to work. I received this message in the console with verbose off “Number of entries reached the size of the hash. Run the program again with a larger has size -hash.”
Welcome,
ThisCanBeSaidWithOptionalRepetitions is actually not supported by RuleORama (I think this is mentioned in the docs and headers) so it is supposed to fall back to a single repetition in that case. In the event that it isn’t actually doing so, you may want to try using the supported grammar declarations (basically, everything that doesn’t have optional repetitions since they blow up the possible grammar size enormously).
For an offline grammar that is actually pretty big – grammars have a much heavier overhead than statistical models so they do need to be smaller in order to perform. RuleORama specifically expects smaller grammars than you could get away with using the stock OpenEars grammar interface, which is a tradeoff in exchange for its faster recognition times.
By the way, ThisCanBeSaidWithOptionalRepetitions around a single ruleset with two obligatory utterances isn’t actually necessary – it just tells the engine that the ruleset will either not be stated, or it will be stated one or more times, but this is the default expectation for any ruleset or statistical model since the user may not speak, or may say the required utterance, or may say it a few times.
Yes, RuleORama was envisioned for smaller grammars than the stock OpenEars grammar tool can handle due to the fact that it provides more speed. This one has > 800 potential utterances so it isn’t a small grammar for RuleORama.
It might work better as a stock OpenEars grammar assuming that you change it so that the numbers equal to and greater than 20 are formed with a rule declaring the base 10 number (i.e.”20″) followed by the numbers 1-9, which lets you avoid a single rule with 100 entries.
Is it correct that OneOfTheseCanBeSaidOnce is being used for both, or does a valid utterance for this grammar actually have to be OneOfTheseWillBeSaidOnce (meaning they are both required)? Having them both be OneOfTheseWillBeSaidOnce will reduce the number of variations a bit. Another thing that might help is reducing to 72 rather than 100, since none of those time measurements (hour, minutes, seconds) are generally dictated in numbers larger than 72.
I would also consider dropping the SECOND/SECONDS plural variations since it doubles the grammar size.
Yes, you can dynamically switch between rulesets, but I would also recommend trying out my suggestions at the end of the previous post (limit numbers to 72, get rid of the plural word variations, and change OneOfTheseCanBeSaidOnce to OneOfTheseWillBeSaidOnce) and see if it ends up with few enough combinations to work. I think that should reduce the ~800 combinations to ~200 which might be small enough to work without a notable impact on the usability of the grammars.
- You must be logged in to reply to this topic.