As expected I made a really stupid mistake. Not loading the attention-types Module.
But at least I understand the system a bit better now. Thanks for the info. regards /Roman On Tuesday, July 26, 2016 at 11:40:44 PM UTC+2, linas wrote: > > There is a numeric value, but it is quasi-hidden. It is assigned when the > module that contains the atom types is loaded. There are current 5 or 6 > modules that define atom types. Hebbian is not in the base module. The > base module is loaded first, and then depending on what you do, maybe some > of the others. The numeric assignment will change, depending on the load > order, and also depending on whether new atom types were add or removed. > This is why the numeric value should be considered to be opaque. > > There's a bit of trickery to make sure that the base types get loaded > first, before any other code runs: the load is defined to run in the > shared-library constructor, so it runs when the shared library is loaded, > before any other code in the shared library runs. Its possible that, with > your dylib loading, you somehow managed to violate this, by not running the > constructor first? However, I believe that the standard glibc dynamic lib > loader "does the right thing" and does run the constructors in the right > order .. so .. I dunno. Add print statements and see what's happening. > Somehow, the load order is screwed up for you, is my guess. > > --linas > > > On Tue, Jul 26, 2016 at 3:52 PM, Roman Treutlein <[email protected] > <javascript:>> wrote: > >> Okay so, I have a ConceptNode and for some reason, the ClassServer >> believes that to be a kind of Hebbian_Links which is obviously wrong. >> >> I really don't know how this could happen and I didn't touch anything >> related to types (as far as I know). Either way the atom_types.script files >> look perfectly fine. >> >> One specific question I have is how the variable/constant HEBBIAN_LINK >> (or NODE) gets its value. It seems to be declared in atom_types.definitions >> but where is it defined? >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/b75cfbb9-b10d-4033-b97c-4510b2a7c8a5%40googlegroups.com >> >> <https://groups.google.com/d/msgid/opencog/b75cfbb9-b10d-4033-b97c-4510b2a7c8a5%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/fb1cc1a9-7328-42d1-a739-37c3d8496ccb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
