wit.ai stories training results unpredictable? -


i trying develop weather bot , have been experiencing problems.

  1. i trained systems stories , in understanding tab. behavior of wit seems unpredictable me - combines stories (which supposed guess), seems converse randomly.
  2. the intent values not consistent either, using same story. used debugger show intent value. example, "what's weather", trained intent value should forecast_all, becomes "what", , other entities other stories shows such "off_topic" entity created off topic conversations. bot behave differently training story.

any insight? doing wrong? did miss? thank help!

i feel pain:)

you have "force" wit.ai correct stories based on user input , if need user follow story till end - have keep "forcing" them down dialogue chain.

what mean this:

if user says what's weather can introduce 1 more custom entity name wth , in understanding tab make keywords based , add strict keywords list related weather word (forecast...).

this "guiding thread". when entity appears = user has used keyword associated weather question = can use entity wth requirement on every action , response of story (actions tab).

in few apps have - each story thought of "what story doing" - what's entry point, , came entity lead user down dialogue path using actions tab , setting only if...always if... requirements on replies , actions.

this approach strict, gives decent level of control on user receives "bot" can anticipate actions , replies.

i playing around approach have lot of stories, "incomplete" trying cover possible different answers user. user starts it's chatting in 1 story, depending on answer - story kicks in, another, another...

also valid, more flexible approach, needs planning of "bot replies" \ stories feel connected in logical, conversational way. , yes needs careful context management because if every story add context - might become big pile of entities , values, need think story adds entity a1 context, if later story b kicks in , adds b1 entity context need remove a1 because conflicting...

to summarize: seems want have bit more control , know dialogue goes. - try actions tab , setting requirements answers , actions. can make straight forward , direct.


Popular posts from this blog

php - How should I create my API for mobile applications (Needs Authentication) -

5 Reasons to Blog Anonymously (and 5 Reasons Not To)

Google AdWords and AdSense - A Dynamic Small Business Marketing Duo