Component Guide II: Containers - Revision history

Rsalter at 18:23, 12 October 2019

2019-10-12T18:23:32Z

← Older revision		Revision as of 18:23, 12 October 2019
Line 61:		Line 61:
	If an input pin is not connected in the parent model, the pin's value is used as a default.		If an input pin is not connected in the parent model, the pin's value is used as a default.

			<span id="clockedchip"></span>
	==Clocked Chip==		==Clocked Chip==
	[[File:clockedchip.png]]		[[File:clockedchip.png]]

Rsalter: /* SimWorld */

2018-10-01T16:49:06Z

SimWorld

← Older revision		Revision as of 16:49, 1 October 2018
Line 192:		Line 192:
	The Connector Pin set of the AgentVector section of the SimWorld adds 2 pins (one input and one output) to the Interface of its element's Capsule type. The new input pin is labeled Init_Count and always appears as Pin 0. This pin is used to initialize the agent set. which in its simplest form involves only setting the initial agent count. (When using certain plugins in interactive mode it also initializes agent position; see, for example, AgentViewerX).		The Connector Pin set of the AgentVector section of the SimWorld adds 2 pins (one input and one output) to the Interface of its element's Capsule type. The new input pin is labeled Init_Count and always appears as Pin 0. This pin is used to initialize the agent set. which in its simplest form involves only setting the initial agent count. (When using certain plugins in interactive mode it also initializes agent position; see, for example, AgentViewerX).

	The special output pin always appears as the first output pin (i.e. on the upper right of the component) and is labeled AData. This pin transmits all agent metadata from the AgentVector section to a corresponding input pin on plugins designed to work with agents ~~(again, see for example, AgentViewerX)~~.		The special output pin always appears as the first output pin (i.e. on the upper right of the component) and is labeled AData. This pin transmits all agent metadata from the AgentVector section to a corresponding input pin on plugins designed to work with agents.

	All other pins correspond to the Interface and use the [[#Common Aggregator I/O Protocol\|Common Aggregator I/O Protocol.]]		All other pins correspond to the Interface and use the [[#Common Aggregator I/O Protocol\|Common Aggregator I/O Protocol.]]

Rsalter: /* CellMatrix */

2018-10-01T16:47:34Z

CellMatrix

← Older revision		Revision as of 16:47, 1 October 2018
Line 160:		Line 160:
	;Using Hexagonal Geometry		;Using Hexagonal Geometry
	[[File:hexmap.png\|thumb\|500xpx\|Raster displaying 20x20 hexagonal geometry]]		[[File:hexmap.png\|thumb\|500xpx\|Raster displaying 20x20 hexagonal geometry]]
	Selecting the '''hexagonal''' array option introduces a hexagonal geometry to the cell array, as shown. In this geometry, the total number of cells is reduced by one-half. Addressing is a shown in the figure, with coordinates restricted so that their sum is an even number.		Selecting the '''hexagonal''' array option introduces a hexagonal geometry to the cell array, as shown. In this geometry, the total number of cells is reduced by one-half. Addressing is as shown in the figure, with coordinates restricted so that their sum is an even number.

	Numerus supports a special set of primops for use with hexagonal CellMatrices.		Numerus supports a special set of primops for use with hexagonal CellMatrices.

Rsalter: /* Overview */

2018-10-01T16:44:23Z

Overview

← Older revision		Revision as of 16:44, 1 October 2018
Line 6:		Line 6:
	Each container type extends and enriches the environment of its elements by assigning new functionalities that are only valid within the context of the container. These new functionalities are introduced through a set of primitive operators (Primops) provided by the Container. (In the language of computer science these kinds of Primops are called '''service providers'''.) The data structure of the container together with the service providers create a topological environment for the constituent Capsules. For example, the CellMatrix container holds a set of Capsules in a lattice or grid structure. Each Capsule is assigned row and column indices, and neighborhoods of Capsules can be identified and manipulated.		Each container type extends and enriches the environment of its elements by assigning new functionalities that are only valid within the context of the container. These new functionalities are introduced through a set of primitive operators (Primops) provided by the Container. (In the language of computer science these kinds of Primops are called '''service providers'''.) The data structure of the container together with the service providers create a topological environment for the constituent Capsules. For example, the CellMatrix container holds a set of Capsules in a lattice or grid structure. Each Capsule is assigned row and column indices, and neighborhoods of Capsules can be identified and manipulated.

	Every aggregator (i.e. a container ~~hold~~ more than one Capsule) assigns some form of identification to each of its constituents. For example, in the case of the CellMatrix, the index pair serves to uniquely specify a particular element. We'll use the term '''Aggregator Id''' to uniformly refer to this identification strategy.		Every aggregator (i.e. a container holding more than one Capsule) assigns some form of identification to each of its constituents. For example, in the case of the CellMatrix, the index pair serves to uniquely specify a particular element. We'll use the term '''Aggregator Id''' to uniformly refer to this identification strategy.

	;Examples:		;Examples:
Line 14:		Line 14:
	*A SimWorld combines an AgentVector with a CellMatrix, so that the virtual agent space of the AgentVector corresponds to the topological space created by the CellMatrix.		*A SimWorld combines an AgentVector with a CellMatrix, so that the virtual agent space of the AgentVector corresponds to the topological space created by the CellMatrix.
	*A NodeNetwork assigns a unique '''Node Id''' to each node of its graph.		*A NodeNetwork assigns a unique '''Node Id''' to each node of its graph.
	*A NetWorld combines an AgentVector with a NodeNetwork so that the virtual agent space of the AgentVector corresponds to the topological space created by the ~~NodeNetork~~.		*A NetWorld combines an AgentVector with a NodeNetwork so that the virtual agent space of the AgentVector corresponds to the topological space created by the NodeNetwork.

	<span id="pins">		<span id="pins">

Rsalter: /* Common Aggregator I/O Protocol */

2018-10-01T16:42:23Z

Common Aggregator I/O Protocol

← Older revision		Revision as of 16:42, 1 October 2018
Line 32:		Line 32:
	Aggregator rules require that all member Capsules must be compatible; that is, they must contain identical Input/Output pin configurations. Consequently,		Aggregator rules require that all member Capsules must be compatible; that is, they must contain identical Input/Output pin configurations. Consequently,
	most<ref>AgentVectors add several special purpose pins.</ref>		most<ref>AgentVectors add several special purpose pins.</ref>
	aggregator Connector Pins correspond directly to some input or output pin in each of the elements: each pin creates a one-to-many input connection or a many-to-one output connection between the Aggregator and some component in the parent Capsule. To provide maximum flexibility the following protocol is used:		aggregator Connector Pins correspond directly to some input or output pin in each of the elements: each pin creates a one-to-many input connection or, respectively, a many-to-one output connection between the Aggregator and some component in the parent Capsule. To provide maximum flexibility the following protocol is used:

	;Input to the Aggregator		;Input to the Aggregator

Rsalter: /* Common Aggregator I/O Protocol */

2018-10-01T16:41:23Z

Common Aggregator I/O Protocol

← Older revision		Revision as of 16:41, 1 October 2018
Line 40:		Line 40:
	;Output from the Aggregator		;Output from the Aggregator
	*The output pin is a function that inputs the Aggregator Id and returns the value for the Output Pin in the element with that Id.		*The output pin is a function that inputs the Aggregator Id and returns the value for the Output Pin in the element with that Id.

			Examples illustrating this protocol will be given below.

	==Chip==		==Chip==

Rsalter: /* Common Aggregator I/O Protocol */

2018-10-01T16:39:25Z

Common Aggregator I/O Protocol

← Older revision		Revision as of 16:39, 1 October 2018
Line 39:		Line 39:

	;Output from the Aggregator		;Output from the Aggregator
	*The output pin is ~~acts like~~ a function that inputs the Aggregator Id and returns the value for the Output Pin in the ~~corresponding~~ element.		*The output pin is a function that inputs the Aggregator Id and returns the value for the Output Pin in the element with that Id.

	==Chip==		==Chip==

Rsalter: /* NodeNetwork */

2018-06-12T16:03:05Z

NodeNetwork

← Older revision		Revision as of 16:03, 12 June 2018
Line 211:		Line 211:
	;Properties		;Properties
	*'''Counts'''. The number of nodes in this NodeNetwork.		*'''Counts'''. The number of nodes in this NodeNetwork.
	*'''Spotlight Node'''. Determines the Node Id used for Spotlighting.
	*'''Initializer'''. In the current version a string identifying the Capsule used to define elements. This string is inserted when a Capsule is dragged over the NodeNetwork, as described above. The string "__bogus__" is used as a placeholder prior to Capsule selection.		*'''Initializer'''. In the current version a string identifying the Capsule used to define elements. This string is inserted when a Capsule is dragged over the NodeNetwork, as described above. The string "__bogus__" is used as a placeholder prior to Capsule selection.
	*'''Connector'''. Determines the connection between the nodes. This may either be a function that decides which nodes have what degree of connection to the others or a single value. If it is a single value all of the nodes will have that level of connection to all of the other nodes.		*'''Connector'''. Determines the connection between the nodes. This may either be a function that decides which nodes have what degree of connection to the others or a single value. If it is a single value all of the nodes will have that level of connection to all of the other nodes.

Rsalter: /* Introduction: Aggregators */

2018-06-12T15:57:29Z

Introduction: Aggregators

← Older revision		Revision as of 15:57, 12 June 2018
Line 76:		Line 76:
	''Abstraction'' is the process of extracting a set of interacting elements which together create a well-defined computation over a given a set of inputs, and providing the ability to access that computation with different inputs from multiple points within the overall project. The simplest example of this in Numerus is the Capsule which is used in one or more chips to implement the instances of a particular submodel. Chips are less useful when large numbers of submodels are required. In such cases it is more efficient to use some form of container to hold a set of Capsule elements. This is analogous to using arrays to manage large sets of data. Like the array, an organizing structure (i.e., the index set) is required to provide a uniform means of access to these constituents.		''Abstraction'' is the process of extracting a set of interacting elements which together create a well-defined computation over a given a set of inputs, and providing the ability to access that computation with different inputs from multiple points within the overall project. The simplest example of this in Numerus is the Capsule which is used in one or more chips to implement the instances of a particular submodel. Chips are less useful when large numbers of submodels are required. In such cases it is more efficient to use some form of container to hold a set of Capsule elements. This is analogous to using arrays to manage large sets of data. Like the array, an organizing structure (i.e., the index set) is required to provide a uniform means of access to these constituents.

	We can actually take this one step further by adding a set of primitive properties and primitive operators that enforce a topological structure on the Capsules. For example, if we organize the Capsules into a two-dimensional lattice, each could represent a single cell in a cellular automaton. In order for this to be		We can actually take this one step further by adding a set of primitive properties and primitive operators that enforce a topological structure on the constituent Capsules. For example, if we organize the Capsules into a two-dimensional lattice, each could represent a single cell in a cellular automaton. In order for this to be of any use, however, each cell must be able to identify its own coordinates and have some means of communicating with other cells in the lattice.
	of any use, however, each cell must be able to identify its own coordinates and have some means of communicating with other cells in the lattice.

	===Element Compatibility===		===Element Compatibility===
Line 101:		Line 100:
	;NetWorld		;NetWorld
	:Combines the topological spaces created by the NodeNetwork and the AgentVector, analogous to the SimWorld.		:Combines the topological spaces created by the NodeNetwork and the AgentVector, analogous to the SimWorld.
			===Visualization===
			Each aggregator has an associated viewer for displaying the state of the aggregator during the simulation run. Viewer properties are programmed using a dialog launched from the properties pane of the aggregator. These are described [[elsewhere]].

	==AgentVector==		==AgentVector==

Rsalter: /* SimWorld */

2018-06-12T15:53:17Z

SimWorld

← Older revision		Revision as of 15:53, 12 June 2018
Line 185:		Line 185:
	;Pins		;Pins

	[[File:example_SimWorld.png\|thumb\|500xpx\|Example ~~of using an AgentViewerX Plugin to visualize a~~ SimWorld (from Hexgrazing in the Model Library]]		[[File:example_SimWorld.png\|thumb\|500xpx\|Example SimWorld (from Hexgrazing in the Model Library]]

	The Connector Pin set of the AgentVector section of the SimWorld adds 2 pins (one input and one output) to the Interface of its element's Capsule type. The new input pin is labeled Init_Count and always appears as Pin 0. This pin is used to initialize the agent set. which in its simplest form involves only setting the initial agent count. (When using certain plugins in interactive mode it also initializes agent position; see, for example, AgentViewerX).		The Connector Pin set of the AgentVector section of the SimWorld adds 2 pins (one input and one output) to the Interface of its element's Capsule type. The new input pin is labeled Init_Count and always appears as Pin 0. This pin is used to initialize the agent set. which in its simplest form involves only setting the initial agent count. (When using certain plugins in interactive mode it also initializes agent position; see, for example, AgentViewerX).
Line 198:		Line 198:

	<br clear=all>		<br clear=all>

	==NodeNetwork==		==NodeNetwork==
	[[File:NodeNetwork.png\|left]]		[[File:NodeNetwork.png\|left]]