Hi people, A top level view of the atomspace values that I can understand:
['Atom', 'AtomSpace', 'FloatValue', 'LinkValue', 'PtrHolder', 'StringValue', 'TruthValue', 'Value', '__builtins__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__pyx_capi__', '__pyx_unpickle_FloatValue', '__pyx_unpickle_LinkValue', '__pyx_unpickle_StringValue', '__pyx_unpickle_TruthValue', '__pyx_unpickle_Value', '__spec__', '__test__', 'createFloatValue', 'createLinkValue', 'createStringValue', 'createTruthValue', 'create_child_atomspace', 'get_refreshed_types', 'get_type', 'get_type_name', 'is_a', 'sys', 'types'] Please can I get a detailed explanation of the generic mechanism for values and secondly, anyone else with interest in seeing the python restAPI work well ? With gratitude, Austin ---------- Forwarded message --------- From: Linas Vepstas <[email protected]> Date: Mon, Apr 15, 2019 at 6:25 PM Subject: Re: Atomspace Package To: Austin <[email protected]> Well, the first step would be to find the REST code, and read through it. Then compare it to the C++ atomspace API's and the to what the wiki says. The biggest, most important aspect is that truth-values and attention-values have gone away, and are replaced by a generic mechanism for values, in general. (well, truth-values and attention-values are still there, but are special cases of the general API.) The most annoying aspect is that REST seems to require the use of "protobuf" for no reason at all (???) which just adds build complexity, and yet another configuration failure scenario. The best way of fixing code is often to simplify it, and I'm guessing that is what the REST API needs -- simplification. A third concern -- performance. Working with the atomspace is really all about speed, and pushing through one-atom-at-a-time, or one-value-at-a-time seems like a major bottleneck. It would be more efficient if the API triggered actions that cascaded thousands of atoms per shot. What are you trying to actually do with it? --linas On Mon, Apr 15, 2019 at 12:10 PM Austin <[email protected]> wrote: > Thank you for your response. I meant The atomspace python module is not > listed as part of the opencog python package. From your explanation I can > see why now. > > Yes Indeed I will love to learn how to contribute towards making the REST > work really well especially. > > Any guides as to where I start ? > > Best, > Austin > > On Mon, 15 Apr 2019 at 17:46, Linas Vepstas <[email protected]> > wrote: > >> Hi Austin, >> >> It is best if you post to the mailing list or provide a github report; >> that way other people can help you. Screen-shots are painful, because it >> is impossible to search for text in a screenshot. The ability to search >> text is a very important debugging tool. I don't know what you mean by >> "the atomspace is missing", you'd have to explain what that actually means. >> >> The biggest problem is that the REST api is unmaintained and out-of-date >> -- it does not support the current programming API's to the atomspace, and >> there are other hints that it's not terribly stable and predictable. We >> need someone who actually understands what REST is to dive into the code, >> clean it up, modernize it and make it work. Would you like to learn how to >> do that? >> >> --linas >> >> >> >> On Mon, Apr 15, 2019 at 4:36 AM Austin <[email protected]> wrote: >> >>> Hi Linas, >>> >>> Hope this email finds you well. I have been trying to work with the >>> atomspace's python RestAPI with no success for a while now. I have >>> installed cogutil, atomspace and opencog with success but checking the >>> opencog package contents, the atomspace seems to be missing; even though I >>> have installed it. Please I will really appreciate any help I can get on >>> this. >>> >>> Best Wishes, >>> Austin >>> >> >> >> -- >> cassette tapes - analog TV - film cameras - you >> > -- 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/CADbdzdwsBvxhVHL93PD_TPzbjJP32rNO1q_AzR8LU7mevg10UQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
