MindForth Programming Journal (MFPJ) jul30mfpj

The MindForth Programming Journal (MFPJ) is both a tool in developing MindForth open-source artificial intelligence (AI) and an archival record of the history of how the AI Forthmind evolved over time.

Fri.30.JUL.2010 -- Basket of Problem Behaviors

With each new MindForth AI coding session, we may reevaluate our list of salient bugs and issues to work on, importing the old list and passing it on for the next coding session.

  • Query "who are you" works as initial but not as secondary input.

  • Inflectional "S" should be added in NLP, not in SpeechAct.

  • Post who-query AI says "I IS I" instead of "I AM I".

  • EnPronoun needs code to choose "he", "she" or "it" based on "mfn".

  • SpreadAct needs a more general search-find-exit coding than "zone".

  • Mechanism for detection of duplicate thought needs removing.

  • BeVerb requires too strict a word order to function;

  • EnArticle kicks in inappropriately with proper name ANDRU;

  • num(ber) of "IS" gets falsely changed from "1" to "2";

  • Entry of "WE" does not convey idea of "YOU AND I".

  • BeVerb supplies wrong form regardless of subject noun number.

Fri.30.JUL.2010 -- Using "fin" to Merge AM IS ARE Forms

In the 27jul10A.F MindForth we finally obtained an AI that could engage in man-machine conversation without major derailments. Perhaps the most glaring problem right now is that "who are you" is answered correctly only when it is the initial query. We want the AI to answer the query properly at any arbitrarily chosen time.

After a few test runs of the new 30jul10A.F source code, we see now at least the cause, but not yet the bugfix, of the glitch where the AI responds to a non-initial "who am i" query with "YOU ARE I". The report captured below shows that the "ARE" verb is acquring a "seq" tag of 50=I which overrides the

108=MAGIC tag at t=371.

367 : 56 39 0 0 107 7 67 56 to YOU

371 : 67 23 0 0 56 8 108 67 to ARE 380 : 108 0 0 0 56 5 0 108 to MAGIC 386 : 55 0 0 0 0 7 67 55 to WHO 390 : 67 23 0 55 55 8 50 67 to ARE 394 : 50 0 0 67 55 7 67 50 to I 396 : 50 0 1 50 0 7 57 50 to I 399 : 57 1 0 50 50 8 33 57 to AM 405 : 33 0 1 57 50 5 57 33 to ANDRU 409 : 55 0 0 33 0 7 67 55 to WHO 412 : 67 0 0 55 55 8 56 67 to ARE 414 : 56 39 1 67 55 7 67 56 to YOU 418 : 56 39 0 56 0 7 67 56 to YOU 422 : 67 47 0 56 56 8 50 67 to ARE 424 : 50 0 1 67 56 7 67 50 to I time: psi act num jux pre pos seq enx

We are beginning to see that present-tense forms of the verb "to be" should not have a "seq" tag, because there is no semantic relationship between the verb as such and the predicate nominative. With a transitive verb, there is indeed such a relationship, because over time a transitive verb such as "eat" may have many direct objects.

We are reminded that in Russian, a present-tense form of "to be" is not even expressed. "KTO OH?", which looks like "Who he?" in English, fully means "Who is he?" to the speaker of Russian. In our AI software, we could leave out the present-tense forms of "to be" and not suffer any more than Russian does. However, we would like some sort of indicator for a verb of being, so that the BeVerb module may be called.

Here is an idea of the moment. We could have the "fin" tag of the present-tense forms "AM", "IS" and "ARE" all go to a verb with psi concept #0 (zero), not as any particular verb form, but as a flag to call the BeVerb module. Once invoked, BeVerb shall have the job of selecting the proper form of "to be" as the output verb.

We went into the Forthmind source code and we added "BE" at the end of the EnBoo t sequence. First we consulted our page on AI standards and we saw 58=BE as a pre-ordained psi-number for the word "BE". We decided to use concept #58 and not #0 (zero) so as to avoid any problems where the software might be testing for a positive (greater-than- zero) psi concept number. We changed the "fin" (fiber-in) tags on "AM", "IS" and "ARE" to fifty-eight (58) so that any such incoming form would activate the #58 "BE" concept -- even though we would use BeVerb to reject "BE" as a word of output and select a proper verb-form instead. We thought that we would have to go into BeVerb and trap for concept #58, but apparently BeVerb only traps for non-BE forms. We ran the AI with two who-queries, and it worked immediately.

Transcript of AI Mind interview at

20 6 29 o'clock on 30 July 2010.

Human: who are you Robot: I AM ANDRU

Human: who am i Robot: YOU ARE MAGIC

Human: User Command: halt

The innovation is such a powerful change to MindForth, that we need to upload the code almost immediately. First we would like to muse that our practice of conducting backwards searches for recent "seq" and other tags, means that a pronoun like "YOU" can be expected "automagically" to refer to the same person who has recently been interacting with the AI. In other words, we do not need immediately to compose code to keep track of different instances of "YOU" in the environment of the AI. The "I" pronoun, on the other hand, can be assumed to refer almost unchangeably to the AI itself.

Mentifex

--

formatting link

Reply to
Mentifex
Loading thread data ...

Give it up Arthur, if you'd spent the last few decades actually working on the code as hard as you self-promote you might have achieved something beyond graduate project level.

Reply to
David Mitchell

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.