Hi Apil, Interesting start. If these were fixed up a bt, they could be published on the website. As it is they are not quite right/misleading.
So -- the atomspace depends on guile and python, so those arrows should point at the atomspace. -- The reasoning agents depend on the atomspace (they are actually a built-in part of the atomspace -- a subcomponent), they do not depend on opencog, nor the cogserver. -- the cogserver provides some low-level network access, it should not be elevated to any special status. Programmers are quasi-welcome to maybe propose and use other network daemons/protocols, instead of the cogserver. -- the cogserver provides the opencog shell. That's the network interface that it provides -- the shell is a subcomponent of the cogserver. You do not have to use the cogserver to get work done. -- the atomspace depends on zeromq, but only if you turn it on. It is one of the alternative network stacks to the cogserver. -- Nothing that I know of depends on opengl, sdl or thread building blocks These are old hold-overs from some old visualization tools that never worked well. These should not appear in the diagram. -- nothing in opencog depends on moses. It should be in the diagram, but currently, its not attached to anything (except that it depends on cogutils) -- only the NLP subsystem depends on link-grammar. -- the atomspace depends on postgres, for save/restore from disk. This is important, and should appear in the diagram. Linas On Thu, Oct 6, 2016 at 8:58 PM, Apil Tamang <[email protected]> wrote: > Hey All, > > So, spent some time researching on the OpenCog architecture. From the > little given in the github/opencog <https://github.com/opencog/opencog> > and github/opencog-docker <https://github.com/opencog/docker> links, I > spawned some high level dependency diagrams of the various subsystems. I am > having a bit of difficulty relating what goes here, but I hope the diagrams > are relatively okay. Also, I'm having a bit of difficulty relating the > docker files to the opencog subsystems. > > I've put some of my questions on the diagrams themselves. Could anyone > take some time to look at it and respond? > > I think it would be a good idea to grow these diagrams in more detail and > clarity. For a newcomer, it is otherwise quite hard to understand how > everything fits into the place. I can work on it while I'm ramping up on > the project. > > Is anyone willing to volunteer like an hour or something over > skype/google-hangout to help me get some traction? There're just a ton of > questions I have about getting setup. > > -- > 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/a5e60576-b68c-48d2-bab3-7431f8eb2278%40googlegroups.com > <https://groups.google.com/d/msgid/opencog/a5e60576-b68c-48d2-bab3-7431f8eb2278%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/CAHrUA361kqPfS6eaHz-pRDEFXciJTcfE-E0mMepvfQXDSLac8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
