Linas Vepštas

Ah thanks. 1) I was working from gc7_6_0 and not HEAD. 2) "real world scenario" for hugepages: well I get these messages, `GC Warning: Repeated allocation of very large block...

The above print is garbled, but then, running the code a second time gives a cleaner print: ``` WW In fibers.scm: ARNING: (guile-user): imported module (fibers) overrides core binding `sleep'...

This may be related to issue #36 except that, for me, running (gc) a bunch of times does not fix the leak. My version of guile is the one that...

My problem is not fixed by the patch provided in issue #36 although it does give me a clean stack trace, unlike the garbled ones above: ``` In fibers.scm: 113:22...

I'll try. My datasets are in a production environment, I'll have to futz around a bit to port everything to a test environment. My understanding of the comments in #36...

Horribly vague and short. This really needs to be elaborated at length. Probably best done on a wiki page somewhere ...

Also, doing this: ``` (use-modules (opencog nlp aiml) (opencog openpsi)) ``` I get ``` ;;; opencog/nlp/aiml.scm:185:12: warning: possibly unbound variable `psi-action?' ;;; opencog/nlp/aiml.scm:219:25: warning: possibly unbound variable `psi-get-exact-match' ;;; opencog/nlp/aiml.scm:254:24:...

well, what makes it so hard to update? If the API changes, why not change it everywhere? When it bit-rots like this, it becomes hard, painful, time-consuming to fix...

FYI, related work: See also https://github.com/opencog/atomspace/issues/1750

@anitzkin Yes, one does need to identify rhemes and themes but not in PLN. PLN knows nothing about sentences or even language. The right way to think of PLN as...