[
https://issues.apache.org/jira/browse/NLPCRAFT-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385958#comment-17385958
]
Aaron Radzinski edited comment on NLPCRAFT-369 at 7/23/21, 6:23 AM:
--------------------------------------------------------------------
Work is done in NLPCRAFT-369. Please review carefully the logic in
{{NCIntentSolverEngine}}.
Here's the all supported intent options in IDL with their default values:
{code:json}
// Intent options in IDL with their default values:
options={
'ordered': false,
'unused_free_words': true,
'unused_sys_toks': true,
'unused_usr_toks': false,
'allow_stm_only': false
}
{code}
Also, please add tests for these conditions. I've only tested the compiler and
hands-on test on Alarm example.
was (Author: aradzinski):
Work is done in NLPCRAFT-369. Please review carefully the logic in
{{NCIntentSolverEngine}}.
Here's the all supported intent options in IDL with their default values:
{code:json}
// Intent options in IDL with their default values:
options={
'ordered': false,
'unused_free_words': true,
'unused_sys_toks': true,
'unused_usr_toks': false,
'allow_stm_only': false
}
Also, please add tests for these conditions. I've only tested the compiler and
hands-on test on Alarm example.
{code}
> IDL intent should support strict flag.
> ---------------------------------------
>
> Key: NLPCRAFT-369
> URL: https://issues.apache.org/jira/browse/NLPCRAFT-369
> Project: NLPCraft
> Issue Type: Task
> Components: model
> Reporter: Aaron Radzinski
> Assignee: Sergey Kamov
> Priority: Major
> Fix For: 0.9.1
>
>
> Basically, the ability to auto-reject (i.e. not match) intent match that is
> ambiguous. By default strict should be 'false'. Right now, it is only
> possible in the callback.
> We also need to remove/replace NCIntentMatch.isAmbiguous() method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
