From OpenCog
Jump to: navigation, search

In OpenCog, an Atom captures the notion of an atomic formula (or atom) in mathematical logic. The primary differences between the concept of atoms in logic, and the concept of Atoms in OpenCog is that OpenCog Atoms have TruthValues that are more general than 'true' or 'false'. Another important difference is that AndLink and OrLink are Atoms themselves, and can be used to combine other Atoms, and so OpenCog does not draw a clear distinction between atomic formulas and atomic sentences: both are given equal footing. Likewise, the ForAllLink and ExistsLink are Atoms that are analogs for the logic expressions x and y, while LambdaLink corresponds to the lambda-calculus notion of λx. Patterns with variables to be grounded are specified using the BindLink.

Because all Atoms in OpenCog carry an immutable type, they are perhaps best understood as terms, in the sense of logic or type theory. Atoms are just type instances, annotated with truth values.

A TruthValue gives each Atom a valuation or an interpretation; thus all Atoms in a given, fixed AtomSpace always carry a default valuation/interpretation along with them. Additional interpretations can be created by using contexts and the ContextLink. When contexts are used, truth values resemble conditional probabilities; that is, the truth value of an atom A in context C can be roughly understood to behave as a probability P(A|C).

The more complex and more general notion of an interpretation or structure in model theory is handled by means of the EquivalenceLink and the SatisfyingSetLink. Atoms can be placed into multiple atom spaces for various convenience calculations.

The EvaluationLink allows a relational model to be specified (again, in the sense of model theory), and thus, the collection of Atoms in an AtomSpace can be thought of as being a generalization of a relational database. In a certain sense, the EvaluationLink is the most central and important atom type in OpenCog, as it is how OpenCog implements knowledge representation.

The atom types page provides a general overview of the various different atom types; see the Category:Atom Types for an index of the atom types currently in use.

Atom Types

Main article: Atom types

All Atoms in the AtomSpace have a type. The two most basic types of Atoms are the Node and the Link. The types form a type hierarchy: all atoms inherit from the type "Atom", and the type Atom itself inherits from ProtoAtom. The ProtoAtom is itself the base type for values (such as truth values) as well as atoms.

The list of supported atom types can be found in Category:Atom Types.

There is an infrastructure for working with atom types: these are the type constructors, of which the TypeNode, the SignatureLink, the ArrowLink and the TypeSetLink are alll examples. Polymorphic types can be specified using the TypeChoice link. The type, and more generally, the signature, can be checked with the type checker.


This page describes the Atom C++ class. For conceptual information, see also OpenCogPrime:Atom.

The type of an atom cannot be changed after the atom has been inserted into the AtomSpace: OpenCog atoms are immutable objects, in the programming-language sense. However, the truth value and the activation can be changed.

Scheme interface

Atoms can be created, manipulated and destroyed at the scheme shell command prompt. See scheme for details.

C++ Programming Interface

Atom is the superclass for Node and Link.

   class Atom {
       inline Type getType();
       stc::vector<Handle> getIncomingSet();

One of the main challenges in implementing the core structures is to have code which allows the representation of knowledge patterns (the graph of nodes and links) in a data structure which was simultaneously very compact (in terms of memory usage), flexible in terms of the kind of allowed queries and time efficient for these queries.

getType() returns the type of the Atom.

getIncomingSet() returns the incoming set of the Atom. The incoming set is explained in the page in Links.

The incoming set is stored inside the Atom as a collection of weak pointers, while the outgoing set is stored in a Link as std::vector of Handles with 'arity' elements.

Atoms are indexed, for fasgt queries, in the AtomSpace. The indexing mechanisms are detailed further in the AtomTable documentation.