Component Guide I: Atomic Components - Revision history

Rsalter: /* Discrete State */

2019-10-14T17:05:21Z

Discrete State

← Older revision		Revision as of 17:05, 14 October 2019
Line 176:		Line 176:
	===<span id="DiscreteState"></span>Discrete State===		===<span id="DiscreteState"></span>Discrete State===
	[[File: discretestate.png\|left]]		[[File: discretestate.png\|left]]
	A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. The possible values for a Discrete State are drawn from some [[NovaScript Introduction#~~DSV~~\|Discrete Value Set]]. A Discrete State is initialized with one such value, and transitions are structured as rules based on the current value.		A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. The possible values for a Discrete State are drawn from some [[NovaScript Introduction#dsv\|Discrete Value Set]]. A Discrete State is initialized with one such value, and transitions are structured as rules based on the current value.
	<br clear="all">		<br clear="all">
	{\|		{\|

Rsalter: /* Discrete State */

2019-10-14T17:04:51Z

Discrete State

← Older revision		Revision as of 17:04, 14 October 2019
Line 176:		Line 176:
	===<span id="DiscreteState"></span>Discrete State===		===<span id="DiscreteState"></span>Discrete State===
	[[File: discretestate.png\|left]]		[[File: discretestate.png\|left]]
	A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. The possible values for a Discrete State are drawn from some Discrete Value Set. A Discrete State is initialized with one such value, and transitions are structured as rules based on the current value.		A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. The possible values for a Discrete State are drawn from some [[NovaScript Introduction#DSV\|Discrete Value Set]]. A Discrete State is initialized with one such value, and transitions are structured as rules based on the current value.
	<br clear="all">		<br clear="all">
	{\|		{\|

Rsalter: /* Component Types */

2019-10-11T20:23:47Z

Component Types

← Older revision		Revision as of 20:23, 11 October 2019
Line 15:		Line 15:

	==Component Types==		==Component Types==
	;Atomic Components:Tranditional systems dynamic components State (subdivided into Stock Stock+Flow, Sequence, Sequence+Flow, and Store), Flow, and Term; along with Command and ~~Event~~.		;Atomic Components:Tranditional systems dynamic components State (subdivided into Stock Stock+Flow, Sequence, Sequence+Flow, and Store), Flow, and Term; along with Command, Event and Discrete State.
	;Containers:Nova containers consist of Chips and 5 types of aggregators; a Chip holds a single instance of [[Modeling_ in_Numerus#capsule\|Capsule]], used as a submodel while aggregators hold multiple Capsule instances, possibly of different types. Each aggregator type implements a different topology for its elements. The aggregator components are AgentVector, CellMatrix, NodeNetwork, SimWorld and NetWorld.		;Containers:Nova containers consist of Chips and 5 types of aggregators; a Chip holds a single instance of [[Modeling_ in_Numerus#capsule\|Capsule]], used as a submodel while aggregators hold multiple Capsule instances, possibly of different types. Each aggregator type implements a different topology for its elements. The aggregator components are AgentVector, CellMatrix, NodeNetwork, SimWorld and NetWorld.
	;Controls and Displays:These include Table, Linechart, Scatterchart, Barchart, Histogram, Slider, Spinner and Toggle.		;Controls and Displays:These include Table, Linechart, Scatterchart, Barchart, Histogram, Slider, Spinner and Toggle.

Rsalter: /* Discrete State */

2019-10-11T20:23:01Z

Discrete State

← Older revision		Revision as of 20:23, 11 October 2019
Line 176:		Line 176:
	===<span id="DiscreteState"></span>Discrete State===		===<span id="DiscreteState"></span>Discrete State===
	[[File: discretestate.png\|left]]		[[File: discretestate.png\|left]]
	A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. A ~~discrete state~~ is initialized with one such value, and transitions are structured based on the current value.		A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. The possible values for a Discrete State are drawn from some Discrete Value Set. A Discrete State is initialized with one such value, and transitions are structured as rules based on the current value.
	<br clear="all">		<br clear="all">
	{\|		{\|
	\|		\|
	;Properties		;Properties
	*'''~~State Names~~'''. ~~States are identified initially as integers 0, 1,~~ .~~.. . Names~~ can be ~~substituted for clarity; note however that these names are constants bound~~ to ~~the integer values,~~ and ~~that~~ the ~~integers~~ are ~~actually still used as state values~~.		*'''Discrete Value Set'''. Each Discrete State assumes values from a Discrete Value Set (DVS). The '''Open DV Set List''' button can be used to view and select from the currently defined DVS's (or to extend with a newly defined DVS). Once a DVS is selected its constituents are listed in the subsequent window.
	*'''Next'''. A tab is provided for each state. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state.		*'''Next'''. A tab is provided for each state to indicate the transition from that state to another of the DVS elements. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state in the DVS.
	\|[[File:discretestateprop.png\|~~349x537~~]]		*'''Init'''. Code entered here determines the initial value of the Discrete State. This code must also evaluate to some legal DVS state.
			\|[[File:discretestateprop.png\|250px]]
	\|}		\|}

	==Notes==		==Notes==
	<references/>		<references/>

Rsalter: /* Discrete State */

2019-10-11T20:11:29Z

Discrete State

← Older revision		Revision as of 20:11, 11 October 2019
Line 180:		Line 180:
	{\|		{\|
	\|		\|

	;Properties		;Properties
	*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.		*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.
	*'''Next'''. A tab is provided for each state. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state.		*'''Next'''. A tab is provided for each state. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state.
	\|[[File:discretestateprop.png]]		\|[[File:discretestateprop.png\|349x537]]
	\|}		\|}

	==Notes==		==Notes==
	<references/>		<references/>

Rsalter at 20:02, 11 October 2019

2019-10-11T20:02:54Z

← Older revision		Revision as of 20:02, 11 October 2019
Line 181:		Line 181:
	\|		\|

	~~===~~Properties~~===~~		;Properties
	*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.		*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.
	*'''Next'''. A tab is provided for each state. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state.		*'''Next'''. A tab is provided for each state. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state.

Rsalter: /* Event */

2019-10-11T20:02:08Z

Event

← Older revision		Revision as of 20:02, 11 October 2019
Line 174:		Line 174:
	*'''Repeated'''. If selected the event will fire each time the condition is true; otherwise it only fires at most once.		*'''Repeated'''. If selected the event will fire each time the condition is true; otherwise it only fires at most once.

	<span id="DiscreteState"></span>~~===~~Discrete State===		===<span id="DiscreteState"></span>Discrete State===
	[[File: discretestate.png\|left]]		[[File: discretestate.png\|left]]
	A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. A discrete state is initialized with one such value, and transitions are structured based on the current value.		A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. A discrete state is initialized with one such value, and transitions are structured based on the current value.
Line 180:		Line 180:
	{\|		{\|
	\|		\|

	===Properties===		===Properties===
	*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.		*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.

Rsalter: /* Event */

2019-10-11T20:01:41Z

Event

← Older revision		Revision as of 20:01, 11 October 2019
Line 173:		Line 173:
	*'''PreUpdate / PostUpdate'''. Determines if the Command runs in the timestep before are after Stocks, Sequences, etc. have been updated to their new values.		*'''PreUpdate / PostUpdate'''. Determines if the Command runs in the timestep before are after Stocks, Sequences, etc. have been updated to their new values.
	*'''Repeated'''. If selected the event will fire each time the condition is true; otherwise it only fires at most once.		*'''Repeated'''. If selected the event will fire each time the condition is true; otherwise it only fires at most once.

			<span id="DiscreteState"></span>===Discrete State===
			[[File: discretestate.png\|left]]
			A Discrete State is an alternative to a Sequence in which a fixed number of named discrete states serve as possible values. A discrete state is initialized with one such value, and transitions are structured based on the current value.
			<br clear="all">
			{\|
			\|
			===Properties===
			*'''State Names'''. States are identified initially as integers 0, 1, ... . Names can be substituted for clarity; note however that these names are constants bound to the integer values, and that the integers are actually still used as state values.
			*'''Next'''. A tab is provided for each state. Code implementing the transition from that state is entered into each tab. The rules for this code are identical to the rules specifying the value of a [[Component_Guide_I:_Atomic_Components#Component_Formulas\|Component Formula]]. The result produced by the code must be another state.
			\|[[File:discretestateprop.png]]
			\|}

	==Notes==		==Notes==
	<references/>		<references/>

Rsalter: /* Term */

2018-08-21T01:28:40Z

Term

← Older revision		Revision as of 01:28, 21 August 2018
Line 117:		Line 117:
	</div>		</div>

			<div id="Term">
	===Term===		===Term===
	The Term component has 6 variations		The Term component has 6 variations
Line 148:		Line 149:
	File:spy_ex.png\|frame\|Spy used to display live count in Game of Life simulation.		File:spy_ex.png\|frame\|Spy used to display live count in Game of Life simulation.
	</gallery>		</gallery>
			</div>

	===Command===		===Command===

Rsalter: /* Flow */

2018-08-21T01:28:14Z

Flow

← Older revision		Revision as of 01:28, 21 August 2018
Line 100:		Line 100:
	</div>		</div>

			<div id="Flow">
	===Flow===		===Flow===
	[[File: flow.png\|left]] A '''Flow''' can be imagined as a pipe that moves content into or out of a Stock. Flows are always connected to Stocks. The Flow's value reprensents the quantity moved by the Flow at each timestep. Positive Flow values move from left to right, or from the black or "negative" end to the red or "positive" end of the connectors. A biflow Flow will flow in the opposite direction when when its value is negative. Flows can be connected at both ends, in which case the Stock at the negative end is decremented and the Stock at the positive end is incremented by the same amount (or vice verse for a biflow Flow with a negative value). Alternatively, a Flow may only be connected at one end (either as an inflow or outflow) in which case the "cloud" symbol represents the unmodeled source or sink of the content. Flow values must be numerical when used with Stocks, but may be any NovaScript data type when used with a Sequence.		[[File: flow.png\|left]] A '''Flow''' can be imagined as a pipe that moves content into or out of a Stock. Flows are always connected to Stocks. The Flow's value reprensents the quantity moved by the Flow at each timestep. Positive Flow values move from left to right, or from the black or "negative" end to the red or "positive" end of the connectors. A biflow Flow will flow in the opposite direction when when its value is negative. Flows can be connected at both ends, in which case the Stock at the negative end is decremented and the Stock at the positive end is incremented by the same amount (or vice verse for a biflow Flow with a negative value). Alternatively, a Flow may only be connected at one end (either as an inflow or outflow) in which case the "cloud" symbol represents the unmodeled source or sink of the content. Flow values must be numerical when used with Stocks, but may be any NovaScript data type when used with a Sequence.
Line 114:		Line 115:
	File:uniflow1stock.png\|Frame\|Uniflow into a single Stock		File:uniflow1stock.png\|Frame\|Uniflow into a single Stock
	</gallery>		</gallery>
			</div>

	===Term===		===Term===