Hi Linas and others, In the meanwhile, I fixed some bugs and superficially tested it on Opera, Chrome and Firefox. I also decided to change the app name to "CogServerLab", if that's ok. The name is unique, and Google Search likes it.
>> And finally, I'd like to hear if the app fulfills criteria for inclusion in the official OpenCog distribution. > Yes, it does. I can't express my gratitude, it is the best Christmas present ever. Thank you very much. > The current procedure is every component get's its own git repo, in this case, https://github.com/opencog/atomizer (or pick a different name, as you wish, let me know.) This repo gets created, and you'd get full read/write privileges to it. So you can send pull reqs and then merge them (without anyone else's involvement) That would be great, could you please open a `cogserverlab` repository, or a directory with the similar name under visualizations project, whichever you prefer (I hope others would be fine with this, too). I'll clone it then, and send a pull request. Also, what license does OpenCog prefer? I'm totally flexible when it comes to licensing. I'd sign the OpenCog foundation in the license file, if that's ok. > It would be fun to load up the atomspace with one of the big datasets, e.g. at https://linas.org/datasets/ and prowl around in that and see what happens. It depends on the amount of RAM. The biggest issue is bitmap caching, so if each oval takes 500 x 500 pixels in average, 4B per pixel, then it is about 1MB per oval, meaning 1GB of free ram should be able to hold about 1000 ovals. In practice, the shallowest oval bitmap is the biggest one, grading down with structure depth. Maybe I could work on this, to remove caching, then it would be more scalable because only visible ovals would take the bitmap memory, but the rendering would be slower and blocking. I'll try to provide both versions (cached and non-cached) switch in a separate configuration file. Other than bitmaps, an s-expression array and its tree structure array are required to reside in RAM all the time. But I'm not sure that mega-sized-datasets are practical examples of using CogServerLab. I imagine some other uses where newbies can play with a few hundreds of atoms while learning how AtomSpace behaves on what Scheme commands in a realtime. It would be also great to see someone making an OpenCog introduction or feature video using CogServerLab. Certainly, I agree CogServerLab wouldn't be the most useful application in the world, but I guess it could be fun to play with. There is also an option of recognizing some raw commands like `vis-only`, to run queries and visualizing only their output instead of the whole atomspace. I have to think about this one, I'm trying to keep the usage complexity at the minimum. --- Otherwise, what is happening with OpenCog Wiki pages? It would be nice to have an objective reference to CogServerLab from there. --- Anyway, great news, and I can't thank you enough, you're the best!. All well, - ivan - pet, 24. pro 2021. u 04:23 Linas Vepstas <[email protected]> napisao je: > > > On Wed, Dec 22, 2021 at 7:27 AM Ivan V. <[email protected]> wrote: > >> >> And finally, I'd like to hear if the app fulfills criteria for inclusion >> in the official OpenCog distribution. >> > > Yes, it does. > > >> If it does, I'm interested in sending a pull request at a place you'd >> find appropriate. >> > > The current procedure is every component get's its own git repo, in this > case, https://github.com/opencog/atomizer (or pick a different name, as > you wish, let me know.) This repo gets created, and you'd get full > read/write privileges to it. So you can send pull reqs and then merge them > (without anyone else's involvement) > > >> it could be fun communicating to OpenCog this way. >> > > It would be fun to load up the atomspace with one of the big datasets, > e.g. at https://linas.org/datasets/ and prowl around in that and see what > happens. > > --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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/opencog/CAHrUA37kKaJXSio4jv-YycGp4tP%2Bdk-5DCCv6eS1F21VoJ4KZg%40mail.gmail.com > <https://groups.google.com/d/msgid/opencog/CAHrUA37kKaJXSio4jv-YycGp4tP%2Bdk-5DCCv6eS1F21VoJ4KZg%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/CAB5%3Dj6UoUAos0PTjSug%3DyvN%3D061eLXbr5q9WJu-pQSMRw9XR3A%40mail.gmail.com.
