-- Hi Reach, I wish I could provide a simple answer but I cannot. So I will try to keep it short.
-- We made a deep and fundamental mistake in not tagging the docker containers with specific version tags. You can work around this as follows: Pick one of the docker containers. Look at it's revision history. Perhaps it was last changed on 24 august 2018. Then ... create a new docker, with the distro appropriate for that date (so, ubuntu 16.04 or maybe 18.04) and then alter all git-clones to fetch the contents of the git repo as it was on 24 august 2018. This feels hacky, and does require some fair amount of work, but should have a high probability of success. -- You are seeing build failures because everyone has lost interest in maintaining the chatbots. This is because they were never awesome to begin with, and because, theoretically-speaking, they are more-or-less a theoretical dead-end (towards creating AGI). They did shine a light on some interesting ideas, and if you were a heavy-hitting programmer with good theoretical chops, we could talk about that... but none of it is easy and all of it is time-consuming. If you just wanted a conventional chat-bot as a toy to play with, I assume the mainstream ones work great. So I assume you want something more than a mainstream toy ... -- There is an effort, on discord, to revive the old blender animated robot head. But that is just the head, no one has attempted to re-attach it to the chatbot. I can send a discord invite if needed. Build failures should be reported on github. There are three possible outcomes: (1) you'll be told that component xyz is obsolete and unsupported (told this almost surely by me), or that (2) there will be no response at all, just silence (no one else is listening and I'm overwhelmed), or (3) it will get fixed (almost surely by me). I'm motivated to provide (3) but sometimes dispense 1 & 2. I keep saying "me", because Ben has pulled almost everyone from off of the projects here, and onto other projects. There are half-a-dozen people kind-of-ish involved, they hang out on discord mostly, none are hacking on the chatbots. I would *love* to have someone excited enough about all this to look it over, report bugs, fix bugs, and actively participate. -- linas On Tue, Aug 23, 2022 at 7:29 PM Reach <[email protected]> wrote: > Every few months I come back to take an attempt at getting a simple > chatbot running so i can do practical experiments to wrap my head around > atomspace and attempting inference. > > My first attempt was the old opencog chatbot. I ran into an alot of build > failures and tried to work them out but ultimately gave up. > > My second attempt, I tried the old chatbot-psi to see if I would have more > luck.. Failures in building too.. > > Lastly I found Mark's noetic/ros-opencog dockerfile and got excited to try > it, but it fails to build too. > > So before I keep trying to forge ahead on paths that may be no longer > viable, I thought I'd ask here: > What's the quickest way to get a running Opencog/atomspace/PLN/URE/NLP > instance running in 2022? a prebuilt docker container from somewhere? a > jupyter notebook? > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/opencog/5cdab71f-0e88-45b0-97ad-0c0beb0486ffn%40googlegroups.com > <https://groups.google.com/d/msgid/opencog/5cdab71f-0e88-45b0-97ad-0c0beb0486ffn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Patrick: Are they laughing at us? Sponge Bob: No, Patrick, they are laughing next to us. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CAHrUA35VrWXDhKXzZs-1AA9jYyh1D2DLoYi6_HzDyM5Oxhcr0Q%40mail.gmail.com.
