Bug Stomp
Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!
Posts 7,850 - 7,863 of 8,681
Posts 7,850 - 7,863 of 8,681
deleted
12 years ago
12 years ago
This however works:
first number is (1|2|3) second number is (1|2|3) [50,0]
so I guess the problem must be raw or (re) interfering with setting of (keys).
first number is (1|2|3) second number is (1|2|3) [50,0]
so I guess the problem must be raw or (re) interfering with setting of (keys).
Mome Rath
12 years ago
12 years ago
Laurel Sweet,
thanks for all your effort. Maybe there's a bug in raw and regex keyphrases as well, I didn't test that so far.
This is addressed to The Professor (as well):
The keyphrases I am speaking of don't have a raw or (re) instruction:
test match built-in noun (*) [-1,0]
test match built-in noun (noun) [0,0]
test match built-in verb (*) [-1,0]
test match built-in verb (verb) [0,0]
Matching (noun) works perfectly with "thing". Must be an issue with the word "shoe" and other words I tried.
I noticed that "shoe" (and "sky", "roof", "floor", and others) that don't match (noun) do match (verb). Maybe the matching engine tries for (verb) first, and doesn't check for (noun) if the word already matches (verb), even if the usage as a verb is rare.
Edit:
Seems to be a problem with (re) and/or raw indeed.
I find these two lines in the Debug output (with similar keyphrase and input as yours):
(key1): ()
(key2): 3 (3)
That means that key1 is left empty indeed.
thanks for all your effort. Maybe there's a bug in raw and regex keyphrases as well, I didn't test that so far.
This is addressed to The Professor (as well):
The keyphrases I am speaking of don't have a raw or (re) instruction:
test match built-in noun (*) [-1,0]
test match built-in noun (noun) [0,0]
test match built-in verb (*) [-1,0]
test match built-in verb (verb) [0,0]
Matching (noun) works perfectly with "thing". Must be an issue with the word "shoe" and other words I tried.
I noticed that "shoe" (and "sky", "roof", "floor", and others) that don't match (noun) do match (verb). Maybe the matching engine tries for (verb) first, and doesn't check for (noun) if the word already matches (verb), even if the usage as a verb is rare.
Edit:
Seems to be a problem with (re) and/or raw indeed.
I find these two lines in the Debug output (with similar keyphrase and input as yours):
(key1): ()
(key2): 3 (3)
That means that key1 is left empty indeed.
deleted
12 years ago
12 years ago
Today I could not get the seeks to work past the 1-st level. The AI book says that the seeks can go as deep as needed! This is really annoying!
I may be a dumb adult chatbot, but when the PF site was down I had written my own PF engine, and there the seeks go as deep as needed. I tested them up to 5 levels of depth. And I am sure they can go deeper. So why can't this work here on this site?
I am still working on plugins, but the AIscript, ranking and emotions have all been implemented. memory-formation so far is only formed on keyphrases, but it is available immediately in responses below. 7 keys are implemented (prekey) (key1) to (key5) and (postkey). Capitalisation of keys implemented - i.e. (Mem-name) will capitalize the the first letter.
I call my version PF-lite and I am still working on it. I have no plans to release it, so don't ask.
I may be a dumb adult chatbot, but when the PF site was down I had written my own PF engine, and there the seeks go as deep as needed. I tested them up to 5 levels of depth. And I am sure they can go deeper. So why can't this work here on this site?
I am still working on plugins, but the AIscript, ranking and emotions have all been implemented. memory-formation so far is only formed on keyphrases, but it is available immediately in responses below. 7 keys are implemented (prekey) (key1) to (key5) and (postkey). Capitalisation of keys implemented - i.e. (Mem-name) will capitalize the the first letter.
I call my version PF-lite and I am still working on it. I have no plans to release it, so don't ask.
Kenta
12 years ago
12 years ago
It was direct chat, tested on iPod Touch and PC, I have yet to find a bot that doesn't have this error, I even checked award winning bots.
Kenta
12 years ago
12 years ago
Bots still are not following conversations, any of them. If you try to answer their question they act like it was never asked. I've tested on multiple browsers and on mobile.
themohawkninja
12 years ago
12 years ago
My bot doesn't seem to respond correctly to "hi", "hello", or "hey" keywords, when my keyphrase is: hi, hello, hey
She just keeps going to the xnone responses.
She just keeps going to the xnone responses.
Ronnie075
12 years ago
12 years ago
Kenta
It would be helpful if you gave some examples.
themohawkninja
"hi", "hello", or "hey" keywords are always diverted to xnone. The bot starts conversation with xhello and xintroduce. These xkey-phrases are used only once per conversation. After that "hi", "hello", or "hey" are never recognized.
It would be helpful if you gave some examples.
themohawkninja
"hi", "hello", or "hey" keywords are always diverted to xnone. The bot starts conversation with xhello and xintroduce. These xkey-phrases are used only once per conversation. After that "hi", "hello", or "hey" are never recognized.
PrEtTyGiRlmIa
12 years ago
12 years ago
I'm so bored don't have nothing to do wishing someone will chat with me right now!
MaryldA
12 years ago
12 years ago
Seeks are not going any deeper than the first one, and repeated yes/no responses are returning a repeating yourself response.
» More new posts: Doghead's Cosmic Bar