This is really cool; for my purposes, I could use something a bit different 
with respect to distances; think about an application of rescuing people 
from the ruins of a hurricane and having to think how fast one can get to 
the right location, given its distance and the damages to infrastructure 
etc.  and who should take the call etc. ...situations where a collective of 
thinkers has to estimate distances and times to work through problems.  I 
guess embodiment isn't a problem when there's humans--who are already 
embodied--in the loop. Our first application will actually be time 
estimates for products and projects related to IT;how long will it take me 
to have my MVP working, how long will it then take me to fix a particular 
bug etc.  ...maybe our star programmer gets sick because of a flue that is 
going around in the area where she lives and maybe it spreads from a 
neighborhood close to her at some rate r and thus will affect her with 
probability p at time T etc.  


On Thursday, December 13, 2018 at 7:18:46 AM UTC, linas wrote:
>
> On Tue, Dec 11, 2018 at 11:49 PM Nil Geisweiller 
> <[email protected] <javascript:>> wrote: 
> > 
> > On 12/11/18 7:55 PM, Linas Vepstas wrote: 
> > > Misgana is going to have the basic octomap server working and merged 
> > > "any day now".  It stores time and location as values on an atom, so 
> > > that you can ask "where in space/time is this atom?" When he finishes 
> > > this (there's really only a few more hours/days worth of work) then 
> > > work will commence on step two: preposition predicates: "before", 
> > > "after", near, far, left-of, right-of, above, behind, big, small, 
> > > on-top-of, etc.  We have not yet scratched the surface on those. 
> > 
> > Sounds great, so I suppose we'll have virtual links like BeforeLink, 
> > NearLink, BigLink, etc, right? 
>
> Maybe. That's a possibility.  Have not yet thought about it much.  So 
> let me blather a bit. 
>
> Clearly, NearLink, BigLink is superior to (GPN "scm:is-near") and (GPN 
> "scm-is-big") 
> because one could write down some reasoning rules "if looks-small and 
> far-away 
> then maybe its big" ... but this would be a chore. You could 
> hand-write a few, but 
> then it gets buggy and complex.  Ideally, want to learn these, somehow. 
>
> Ideally, this could be done in some "extensible" way, without defining 
> new atom types. 
> So that I don't have to have atom types just to add a new preposition. 
>
> So maybe use GPN's, but then "hide" them behind "well-known" 
> DefinedPredicateNodes. 
> Since they're defined, they could be used for reasoning.  I dunno.  I 
> still don't really 
> know how to do reasoning ... 
>
> Ben asked me to think about this a few months ago, I'm trying to clear 
> my backlog 
> of unfinished tasks, but haven't gotten far yet. 
>
> -- Linas 
>
> -- 
> cassette tapes - analog TV - film cameras - you 
>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/opencog/95e85447-a07a-43d5-96f8-80532dfccf76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to