On Thu, May 30, 2019 at 3:25 PM buj wrote:
> Upon further study, I have become quite confused on atomspace's type
> system. Let me explain:
>
> I was on my quest to understand which links are executable, and which are
> evaluatable. So I came across various resources: the scheme command
>
I converted this email to a brand-new intro for the wiki page
https://wiki.opencog.org/w/AtomSpace#Overview
-- linas
On Thu, May 30, 2019 at 3:01 PM Linas Vepstas
wrote:
> Hi Jack,
>
> Wow! I welcome the effort, its nice to have projects influence one-another.
>
> I would like to point out
Hi Jack,
I looked over the google-docs document on anticipatory machine reading. You
might get new insight from reading
http://www.coli.uni-saarland.de/courses/syntactic-theory-09/literature/MTT-Handbook2003.pdf
Sylvain
*KAHANE 's* review of Meaning-Text theory. I think you will enjoy the way
Hi Jack,
Wow! I welcome the effort, its nice to have projects influence one-another.
I would like to point out something: to **understand** the atomspace,
reading the source code is probably the hardest, most confusing, and
misleading way of doing it (as in there lurks bugs and occasional bad
Hi Jack,
If Java complains that something is not in "java.library.path" it means
that ".jar" package you loaded tries to load native (JNI) shared library
and cannot find it.
In the case it complains that it cannot find "liblink-grammar-java.so"
library.
First of all you may check if this file
Since I have limited experience with c/c++, but some ability to
transliterate other programs to Java, I decided to build a Java version of
AtomSpace solely to better understand how AtomSpace is supposed to work.
The project is far from functional but already is helping me understand
this
Hi Vitali and Linus
> Ran configure, then make clean. Here's the trace for java-jni
>>
> make[2]: Entering directory
'/home/jackpark/Downloads/link-grammar-5.6.1/bindings/java-jni'
CC jni-client.lo
CXXLD liblink-grammar-java.la
ar: `u' modifier ignored since `D' is the default (see `U')
Hah! After the clean make, Linus's suggestion to add
-Djava.library.path=/usr/local/lib to the VM args in Eclipse did the trick.
I have exercises which pass the same sentence directly to the parser and to
RelEx; both exercises run just fine.
In a different thread, I'll explain what I am working
