Perhaps I should just join discord. If Ben has moved folks to other tasks, where is the activity these days that was once here? I've noticed this list isn't as busy as it once was.
On Wed, Aug 24, 2022, 2:09 PM Jacques Basaldúa <[email protected]> wrote: > >>So please don't say "old" -- it's the real deal, its what actually works > *right now*. > > Sorry for that. I said I was not qualified and have just been playing with > it. > > It was easy to get opencog running. With that, the curious user can go to > the scheme interpreter by typing `scm` and import it like `(use-modules > (opencog))` as described in: > https://wiki.opencog.org/w/Getting_Started_with_Atoms_and_the_Scheme_Shell > > > On Wed, Aug 24, 2022 at 6:51 PM Linas Vepstas <[email protected]> > wrote: > >> Hi Jacques, >> >> Yes, this works great. However, it's just the bare-bones system; the >> chatbots are not enabled/configured. The robot head won't start up. >> >> Also, it is not the "old opencog", despite all the hype about hyperon. >> Large and important parts of the subsystem are not only supported, but are >> in active development. I'm working hard on making certain subsystems much >> better. Others are involved too. I think that the "important" parts will >> live on, get ported/interoperable with hyperon if/when that ever matures. >> So please don't say "old" -- it's the real deal, its what actually works >> *right now*. >> >> However, there actually are parts that are "old", abandoned, with no >> plans to revive or replace them, Those have been split off into distinct >> git repos, and are mostly clearly marked as old or abandoned. >> >> --linas >> >> >> On Wed, Aug 24, 2022 at 1:21 PM Jacques Basaldúa < >> [email protected]> wrote: >> >>> I am not qualified to answer this, but I will share my experience as a >>> user who just played with the old opencog. Setting it up was very >>> straightforward. >>> >>> I just git cloned: >>> >>> https://github.com/opencog/docker.git <repo> >>> >>> Where <repo> is a better name than "docker". >>> You can find complete instructions in the markdowns, I just walk you >>> through the minimum. >>> Running a server is just three steps: >>> >>> cd <repo>/opencog >>> ./docker-build.sh -a >>> cd cogserver/ >>> docker build --no-cache -t opencog/cogserver . >>> docker run -p 17001:17001 -it opencog/cogserver >>> >>> Wait for the "Listening on port 17001" message. >>> >>> Connecting to it is just one (assuming rlwrap is installed). >>> >>> rlwrap telnet localhost 17001 >>> >>> My 2 cents. >>> >>> >>> >>> >>> >>> >>> >>> On Tue, Aug 23, 2022 at 6: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> >>>> . >>>> >>> -- >>> 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/CA%2B_pmb51c0cS-RCyS-DA0%2Bv2nPSuxjEJBA8xQyU2vfkFteWSwA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/opencog/CA%2B_pmb51c0cS-RCyS-DA0%2Bv2nPSuxjEJBA8xQyU2vfkFteWSwA%40mail.gmail.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/CAHrUA35rddyQZC17ORQWZhnpFMOR7%2BcOzF%3Dd8dOHAHyQsud6bw%40mail.gmail.com >> <https://groups.google.com/d/msgid/opencog/CAHrUA35rddyQZC17ORQWZhnpFMOR7%2BcOzF%3Dd8dOHAHyQsud6bw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CA%2B_pmb5SnmCAFEdjfyc9eHK4BORM6SxCRojN_cFKvAyGe-ztKw%40mail.gmail.com > <https://groups.google.com/d/msgid/opencog/CA%2B_pmb5SnmCAFEdjfyc9eHK4BORM6SxCRojN_cFKvAyGe-ztKw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAOSHuKu0UoX9KUSrU8XScdSEUqHK08qO4wiFLsik24czTF2ZRQ%40mail.gmail.com.
