| home | user guide | examples | reference | changelog | resources |
A vector cable for connecting _CMLINK(assembly, AssemblyItem, AssemblyItems). Vectors are implemented as one dimensional arrays of doubles with no other information. The length may change while a model is running. Vector connections work only in request mode. When a connection is established between two components, the source is registered with the target as a vector provider. The latter then queries the source component whenever necessary for the current vector, fetching either the whole vector or requesting the value of a single component.
A cord for physically connecting components. The simplest real-world analogy to a cord is a piece of string or tape. It is used, for example to bind together sensors and effectors within the same _CMLINK(world,Body,animat) to indicate that they all move together within a virtual environment. It is also used to connect the sites of a _CMLINK(world, TrajectorySite, trajectory), somewhat like the ropes used to channel people around airport queues.
A tube for moving solutions around. Tubes are generally implemented as having negligible volume, so whatever is applied at one end immediately appears at the other. They are also normally uni-directional, as though they contained one-way valves, but this depends on the application.
An arrow for indicating that one component is inserted in another. The InsertionArrow occurs in a number of contexts, all related to models of physical objects. For example, a _CMLINK(cell, SynapsePopulation) population of synapses is connected to a _CMLINK(cell, IntegratorCompartment, cell body) by an insertion arrow. It indicates that the synapses belong in the membrane of the target cell. Another use of the insertion arrow is in virtual environments where objects are attached to particular places in an environment (_CMLINK(world, InsertionSite, insertion sites)) or where an animat is attached to a _CMLINK(world, TrajectorySite, trajectory point) to indicate where it starts.
Objects go through object pipes. Among the types of object that can be generated are connectivity matrices and parameter listings.
A spike propagating cable for connecting _CMLINK(assembly,AssemblyItem,AssemblyItems). Spike cables work in event-driven mode: when the source component generates and event it is immediately delivered to the target component. Each event has a time and an integer index, so the SpikeCable is a multi-channel device. Certain receiving components ignore the spike index, whereas most will interpret spikes differently according to their index.