Alright, sounds good! I have one question that is more of the source for my trouble getting into opencog. I am pretty used to looking at small projects on github and I’m usually able to find all the scripts under one repository. With opencog, the project is super large and from what I can tell, it is not all in one repository. Is there an easy way for me to find all of the open source code so that I can piece it all together in my mind. I want a better picture of how all the scripts and parts work together...
--
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 opencog+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
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/266b1a63-f29e-41cd-9983-12cda5d0a3dd%40googlegroups.com.
--
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 opencog+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
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/266b1a63-f29e-41cd-9983-12cda5d0a3dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Ok, so from what I’ve gathered, it seems like I have to build opencog before I can analyze the code. Is this correct?
--
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 opencog+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
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/78193911-5844-4be5-8432-66805d92841f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Tue, May 28, 2019 at 10:53 PM Daniel <danex...@gmail.com> wrote:Ok, so from what I’ve gathered, it seems like I have to build opencog before I can analyze the code. Is this correct?If you are interested in the guts of the current code, and if you can't build it, you will be lost forever. Being able to build the current code base is a necessary prerequisite for doing anything with it (including "understanding" it)If you are interested in bringing old, dead code back to life (e.g. the old docker repo I pointed at), then "understanding it" is an iterated process of figuring out why it won't build, and then figuring out a fix for that, repeated ad-infinitum.If you want to just read the wiki -- you can, but it's not much fun if you can't run the examples. And, to run the examples, you have to build it first :-)--linas
--
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 ope...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
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/78193911-5844-4be5-8432-66805d92841f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I was able to build the code on a stand alone instance of ubuntu. That was last year before i was hit with some personal issues. I'd like to jump back into the code base, where is the link to the docker image? that would be the most promising build process from a software engineering standpoint. I'd like to give it a try.
--
On Wednesday, May 29, 2019 at 1:42:26 AM UTC-4, linas wrote:On Tue, May 28, 2019 at 10:53 PM Daniel <danex...@gmail.com> wrote:Ok, so from what I’ve gathered, it seems like I have to build opencog before I can analyze the code. Is this correct?If you are interested in the guts of the current code, and if you can't build it, you will be lost forever. Being able to build the current code base is a necessary prerequisite for doing anything with it (including "understanding" it)If you are interested in bringing old, dead code back to life (e.g. the old docker repo I pointed at), then "understanding it" is an iterated process of figuring out why it won't build, and then figuring out a fix for that, repeated ad-infinitum.If you want to just read the wiki -- you can, but it's not much fun if you can't run the examples. And, to run the examples, you have to build it first :-)--linas
--
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 ope...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
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/78193911-5844-4be5-8432-66805d92841f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--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 opencog+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
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/d34aa68b-d2d0-4f3e-a08c-8778a8ac0258%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.