![\"\"](\"https:\/\/test.warrensoft.co.uk\/wp-test\/wp-content\/uploads\/2017\/10\/PhraseProcessorBlockDiagram-300x232.png\")
<\/p>\nAs the name suggests, the Phrase Processor processes a phrase and returns a response. If the phrase is a call to action, then the action is performed and a confirmation forms the response. Here is a block diagram.<\/p>\n
<\/p>\n
The real work is performed by the Functions<\/em>, which talk to the hub to find out the current kitchen temperature, or to switch on the heating, etc.<\/p>\n The Input Substitution<\/em> converts everyday terms into terms the hub will understand e.g. rain > precipitation, etc. \u00a0Similarly, the Output Substitution<\/em>\u00a0can change words that are not pronounced well by the Text-To-Speech component e.g. Beaufort > Bofort.<\/p>\n Candidate Extraction<\/em> involves splitting a phrase into likely candidate terms. For example, we may have a zone called Bedroom 1, so if we were to utter the phrase ‘what is the humidity in bedroom 1<\/em>‘, our tokenizer might spot humidity as a measurand, but might not recognise bedroom 1 as a zone. By using a word count of 2, we can extract the following candidate terms: what, what is, is the, .. , bedroom 1 and we have a fighting chance our zone will be spotted.<\/p>\n The Tokenizer<\/em> takes candidate terms and looks them up in lists of terms. Term lists are read from the hub: sensor names, zone names, actuator names, measurands, etc. or derived from pre-configured command lists. It then generates a set of tokens which provides automatic de-duplication.<\/p>\n The Signature Builder<\/em> converts the set of tokens into an ordered function signature and marshals the parameters. \u00a0So taking our example from above, the tokenizer would have generated a humidity measurand token and bedroom-1 zone token. These would be converted into the measurand_zone( x, y ) function signature, and the function would be called. This approach allows us to utter the reverse phrase ‘bedroom 1 humidity’ and still have it handled by the same function.<\/p>\n Specific sensors can be configured to report\u00a0supplementary<\/em> information for certain value ranges. For example, wind speed in mph can be supplemented with a familiar description e.g. 40 mph plus\u00a0gale, 8 on the Beaufort\u00a0scale.<\/em><\/p>\n This covers the structure of the Phrase Processor. In the next post we will address minor changes we need to make to the home-hub to be able to implement the REST interface.<\/p>\n","protected":false},"excerpt":{"rendered":" As the name suggests, the Phrase Processor processes a phrase and returns a response. If the phrase is a call to action, then the action is performed and a confirmation forms the response. Here is a block diagram. The real work is performed by the Functions, which talk to the hub to find out the … <\/p>\n