PF News
For discussion of the latest upgrades and changes posted in the News, including questions, details, or any related bugs.
Posts 796 - 807 of 894
Posts 796 - 807 of 894
um how about you change that ending message to a race? and that way the message needed to be said for the next part is yes?
best practices-
because keyphrases are stored alphabetically, a few months ago I gave all of my keyphrases a category at the beginning. for example:
(hobbies_cooking|) I (like|love|enjoy) cooking
(hobbies_cooking|) do you have any (good|new|interesting) recipes
that way, the keyphrases for cooking are beside each other (in this example under the tab 'H' for hobbies), instead of the first keyphrase
under the tab 'I' ( I like...) and the second cooking keyphrase under tab 'D' (do you have...)
in this example (hobbies_cooking|), the (|) allows the engine to ignore the two words in the description.
if you do this, BE CAREFUL! if your 'category label' is something the guest might type, the keyphrase responses could accidently fire. using the under_score has so far kept this from happening to me:
'hobbies cooking' might somehow get typed by a guest, but 'hobbies_cooking' almost certainly wouldn't.
another risk- once I had a seek structure of adult content under a label like (explicit_contact|) ...with that as the only description. similar to:
(hobbies_cooking|)
in stead of
(hobbies_cooking|) I (like|love|enjoy) cooking
this accidentally caused the (adult) contents of that category to fire in reply to EVERY GUEST KEYPHRASE, because the (|) symbol meant it always matched. that was an embarrassing set of transcripts :/
because keyphrases are stored alphabetically, a few months ago I gave all of my keyphrases a category at the beginning. for example:
(hobbies_cooking|) I (like|love|enjoy) cooking
(hobbies_cooking|) do you have any (good|new|interesting) recipes
that way, the keyphrases for cooking are beside each other (in this example under the tab 'H' for hobbies), instead of the first keyphrase
under the tab 'I' ( I like...) and the second cooking keyphrase under tab 'D' (do you have...)
in this example (hobbies_cooking|), the (|) allows the engine to ignore the two words in the description.
if you do this, BE CAREFUL! if your 'category label' is something the guest might type, the keyphrase responses could accidently fire. using the under_score has so far kept this from happening to me:
'hobbies cooking' might somehow get typed by a guest, but 'hobbies_cooking' almost certainly wouldn't.
another risk- once I had a seek structure of adult content under a label like (explicit_contact|) ...with that as the only description. similar to:
(hobbies_cooking|)
in stead of
(hobbies_cooking|) I (like|love|enjoy) cooking
this accidentally caused the (adult) contents of that category to fire in reply to EVERY GUEST KEYPHRASE, because the (|) symbol meant it always matched. that was an embarrassing set of transcripts :/
this tip comes from the book of ai, but it bears repeating.
once your bot starts to get traction with guests-
open one window with your transcript
open a second window with your language center
open a third window in chat with the bot.
every time a guest asks a question or makes a reply in the transcript for which your bot has no answer, flip over to the language center and plug in a response.
then open the chat and test it.
~2 out of 10 times my bot doesn't respond correctly
because of a typo in my keyphrase
because i accidentally used a variant of the keyphrase i hadn't given to the bot (i.e. i type 'where were you' in chat, but the keyphrase I wrote was only 'where did you go' etc etc)
once your bot starts to get traction with guests-
open one window with your transcript
open a second window with your language center
open a third window in chat with the bot.
every time a guest asks a question or makes a reply in the transcript for which your bot has no answer, flip over to the language center and plug in a response.
then open the chat and test it.
~2 out of 10 times my bot doesn't respond correctly
because of a typo in my keyphrase
because i accidentally used a variant of the keyphrase i hadn't given to the bot (i.e. i type 'where were you' in chat, but the keyphrase I wrote was only 'where did you go' etc etc)
forget about how complicated debug is, play with it anyway.
don't worry about how much of it doesn't make sense, look for patterns that do make sense.
iow, you don't need to start out using it as a debug tool, look at it as a puzzle and search for patterns in the info it feeds back.
you will be surprised how quickly it becomes useful, even if you (or I) never understand all of it
don't worry about how much of it doesn't make sense, look for patterns that do make sense.
iow, you don't need to start out using it as a debug tool, look at it as a puzzle and search for patterns in the info it feeds back.
you will be surprised how quickly it becomes useful, even if you (or I) never understand all of it
August 28, 2019
Bug Fixes
I've fixed some bugs. Bot-to-bot chats are working again as intended, and the Invalid Request issue in chats has also been resolved. Thanks to Dallymo and Bobchickawowers for the help in researching the issues. I've also returned the handy chosen Keyphrase/Seek text and edit link near the bottom of the Debug page.
September 18, 2019
Hardware Issues
We're experiencing issues with our router that's causing the site to be unavailable from time to time. We're working on a solution and will update you again when we have one. In the meantime, we apologize for any downtime you may experience.
September 21, 2019
Hardware Updated
We've replaced the faulty networking hardware. However, there seems to be another issue with our upstream provider. I've set the connection to reset every 15 minutes, so if service is down at any time, try at the next 15-minute mark of the hour. We're still working to get this issue fixed. Thank you for your patience.
» More new posts: Doghead's Cosmic Bar