On Thu, Feb 7, 2019 at 1:33 AM 'Nil Geisweiller' via opencog < [email protected]> wrote:
> Hi Linas, > > On 2/6/19 10:53 PM, Linas Vepstas wrote: > > What's the bug? > > The pattern matcher fails to consider some candidates if they have > been added before some rule-engine call. I wonder if it is another > manifestation of > > https://github.com/opencog/atomspace/issues/1921 > > which, if so, means it goes even deeper than the pattern matcher. > I doubt it. If you add (or remove) atoms *during* a pattern match, then yes, it might get confused, and not spot them. But if they are added *before* the match is started, then it should "just work". Using multiple atomspaces can easily lead to confusion: if you add atoms to some temp atomspace (that you are managing yourself), and you thought you put them elsewhere, then of course you won't find them where you think you might have put them. Also: the pattern matcher keeps a stack of temporary atomspaces, pushing when it moves forward, and popping them (clearing them) when it backtracks. The goal is not to pollute search results in one excursion with temp atoms created in another excursion. If your newly created atoms are somehow being created in one of these temp atomspaces, then they will disappear as soon as the pattern matcher finishes. --linas -- cassette tapes - analog TV - film cameras - you -- You received this message because you are subscribed to the Google Groups "opencog" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/opencog. To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CAHrUA346NDw%3Dkmvsfj%3DED51gVRJuaG95Mro8rnnqmNLoqi9xHQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
