Hi Xabush, So I have a tough question for you: the MOZI webserver ...
I'm trying to solve a meta-problem: I want to increase developer engagement in opencog/atomspace. For that, it would be nice to have a web UI. Three of them actually, or four. 1) A web UI that allows users to create new atomspaces, and put (by hand) some atoms into it, and visualize simple graphs. So, people can point their browser at it, and mess around. 2) A job control panel web UI. So, for the language learning project, I have a collection of bash scripts that start and stop the atomspace, and ingest text files, and take hours or days to run. I thought of MOZI because it has some similar requirements. 3) A data explorer. Given an atomspace, with say, millions of atoms (from language learning, or from biochem), I want to explore what's inside of it: print all atoms in some cluster, ranked by frequency, or plot some histogram of mutual information vs frequency or whatever. Maybe a kind-of-like jupyter for the atomspace. Again, I think of the MOZI work in this direction. You were trying to get a simple web UI for biochemists to use. I want the same deal, but for linguists. Under the covers, it's all the same stuff: just atoms in the atomspace. How can this be accomplished? You've built some kind of custom solution for 2 & 3 for MOZI, but I don't understand how to backtrack out of that, and custom-tailor it so that it works for language learning instead of ChEBI or PubChem. Any ideas? I mean, you and Hedra have put a lot of effort into these things... I see things like this: https://github.com/MOZI-AI/annotation-service and this: https://github.com/MOZI-AI/annotation-service-ui And I'd like to have it work for the kinds of graphs and systems in the language-learning codebase, instead of biochemistry. What would it take to have that work? Do I really have to start from scratch? Is there a way to recycle any of the work that you've done, and use it for other applications? I don't want to go off and state the obvious, but maybe I should go off and state the obvious: if this web UI stuff was generic, then other users could use it, which means that other users could show up and help fix bugs and add features. It would grow the project overall ... it would help anyone interested in the atomspace and in singularitynet and all that jazz ... BTW, back in the days of Hanson Robotics, we had the same problem ... I think we throw a lot of money at some Brazillian to create a WebUI for the Owyl behavior tree subsystem, but .. of course, that code failed with the AtomSpace, so it was like .. wasted money, wasted effort. .. we still don't have a generic AtomSpace WebUI ... -- Linas -- 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/CAHrUA355C6jVfExiFaqYusBxj4oGwD2Bpd%2B9DY7qP3jyLb7orQ%40mail.gmail.com.
