Epstein Secrets

r the latter are learned via MOSES or via some other means. The textual realization of Combo resembles LISP with less syntactic sugar. Internally a Combo program is represented as a program tree. • Composer: In the PLN design, a rule is denoted a composer if it needs premises for generating its conse

ve its fingers to pick up a cup, coordinating its movements with its visual perceptions. It's certainly possible to represent this sort of thing in Combo, but Combo may be an awkward tool. However, if one represents low-level procedures like this using another method, e.g. learned cell assemblies in a

the question of programs in what programming language, and in this context we have made a fairly traditional choice, using a special language called Combo that is essentially a minor variant of LISP, and supplying Combo with a set of customized primitives intended to reduce the length of the typical p

get processor time, at which point in time. • Schema: A "script" describing a process to be carried out. This may be explicit, as in the case of a GroundedSchemallode, or implicit, as the case in Schema maps or ungrounded Schemallodes. • Schema Encapsulation: The process of automatically recognizing a Schema Map

tricks, fetch_ball and triple_kick to be described below. in order to calibrate the size penalty function: 1. fetch_ball, which corresponds to the Combo program and_seg (goto (ball) grab (ball) goto (owner) drop) 2. triple_kick, if the stick is near the ball then kick 3 times with the left leg an

n x, two possibilities exist: EFTA00624385 33.6 Hierarchical Program Learning 239 • There is already a model for PredicateNodes at position x in Combo trees in the given population, in which case a population of PredicateNodes potentially living at that position is drawn from the known model, and

PLN Rules as GroundedSchemallodes PLN inference rules may be represented as GroundedSchemallodes. So for instance the PLN Deduction Rule, becomes a GroundedSchemallode with the properties: • Input: a pair of links (LI, L2), where LI and L2 are the same type, and must be one of InheritanceLink, ImplicationLink, Sub

uesses produced by pure procedure learning methods), it may still be valuable to have this procedure in compact and rapidly executable form such as Combo provides. To proceed with the technical description of predicate schematization in CogPrime. we first need the notion of an "executable predicate".

tand: all else equal, a predicate embodied in a small Combo tree is better than a predicate embodied in a big one. There is some work hidden here in Combo tree reduction; ideally, one would like to find the smallest representation of a given Combo tree, but this is a computationally formidable problem

asic backward step to carry out variable fulfillment queries as well as truth value queries. We may encapsulate these processes in the Atomspace as GroundedSchemallode: BasicForwardlnferenceStep GroundedSchemallode: BasicBackwardInferenceStep which take as input some Atom Al. and also as GroundedSchemallode: Att

r the latter are learned via MOSES or via some other means. The textual realization of Combo resembles LISP with less syntactic sugar. Internally a Combo program is represented as a program tree. • Composer: In the PLN design, a rule is denoted a composer if it needs premises for generating its conse

p the rules might profitably be ported into the Atomspace as ImplicationLinks. • Representation Building: A stage within MOSES, wherein a candidate Combo program tree (within a deme) is modified by replacing one or more tree nodes with alternative tree nodes, thus obtaining a new, different candidate

get processor time, at which point in time. • Schema: A "script" describing a process to be carried out. This may be explicit, as in the case of a GroundedSchemallode, or implicit, as the case in Schema maps or ungrounded Schemallodes. • Schema Encapsulation: The process of automatically recognizing a Schema Map