Can you please post an excerpt or an example? Thanks
On Monday, October 7, 2019 at 11:34:41 AM UTC+3, Nil wrote:
>
> Fellow C++ dev, just a warning after being brought to the edges of
> madness by the following bug (item 2)
>
> https://github.com/opencog/miner/pull/14
>
> TL;DR version:
>
>
Yeah, email is fine. Although, I find it to be cumbersome and unintuitive
for dev discussions but that's just me.
Anyways, I have downloaded an ssb client app, setup a username (xabush) and
joined a pub (https://ssb-pub.picodevelopment.nl/). I've also subscribed to
#opencog channel.
On
C+3 linas wrote:
> On Tue, Sep 8, 2020 at 3:32 PM Abdulrahman Semrie
> wrote:
>
>> Great write up Linas!
>>
>> I'm fuzzy on the formula for the size of vertex and edge tables on page
>> 6. It'd be great if you added an explanation to make it more
variants.
—
Regards,
Abdulrahman Semrie
> On Thursday, Aug 27, 2020 at 9:43 PM, Linas Vepstas (mailto:linasveps...@gmail.com)> wrote:
>
>
> On Thu, Aug 27, 2020 at 12:55 PM Abdulrahman Semrie (mailto:hsami...@gmail.com)> wrote:
> > > A second is to create a
point is, again, this stuff has real implications for
>> usability and computability, e.g. for Ben's latest Hyperion ideas, and so
>> it would be nice to get the facts and the numbers correct, so that it
>> doesn't look like we're blowing fumes.
>>
>> --
In the current atomspace, atoms are indexed by their type, i.e given a type
we can retrieve all the atoms that have that type. But there is no other
away of adding custom indices in the atomspace. For example, if we want to
index nodes by their name, there is no way of doing this.
As
es only 25.8 seconds to load
with ~ 2GB of RAM usage.
I use the sexpr code
(https://github.com/opencog/atomspace/tree/master/opencog/persist/sexpr) to
load them which is much faster than using guile’s primitive-load.
> How do you run them?
I didn't understand this question.
—
Regards,
Abd
name from the
atomspace, there is no way to cache/index. If there was some ExistsLink that
inherits from QueryLink where you can use to retrieve an atom by its name if it
exists or return a false truth value, then what you’ve described can be done.
—
Regards,
Abdulrahman Semrie
> On Thursday,
for (Concept "the-set-of-all-uniprots") and what the pattern
>>> matcher "actually does" is to stitch together these partial indexes into a
>>> whole, and then prune away the irrelevant parts.
>>>
>>> -- Linas
>>>
>>> ... unless
> I think it's a mistake to try to think of a distributed atomspace as one
super-giant, universe-filling uniform, undifferentiated blob of storage.
It is not clear to me why this is a mistake. It obviously has its use
cases. When I think of a distributed atomspace, I think of multiple
Hi Linas,
(Sorry for not responding earlier. As Mike have explained, I'm on vacation
and don't check my e-mail regularly. I should be able to answer more
questions when I'm back next week)
More or less, the three requirements that you mentioned above have either
been partially implemented (1)
> There is now a new Atom type: (StorageNode "some://
example.com/url/where?ever") When you open it, you can send Atoms to that
URL, or receive them, or even run pattern queries on the remote system, and
get back only the matching results. You can have as many of these open as
you want, and so
12 matches
Mail list logo
