this.name

The name of the global variable that will be storing this instance of the class.

holds the dimensions’ names for interface purposes

agentset, contains all agents that are at the node

bool, true as long as node is active.

bool, indicating wether costs/benefits depend on agent’s node-condition-once

bool, indicating wether costs/benefits depend on agent’s node-condition-repetitive

ordered list, contains values for different dimensions node-costs-benefits-agents-control-factor-per-technology -table of ordered lists, indexed by technology-names.

ordered list, contains values for different dimensions node-costs-benefits-technology-dependencies: vector, indicating for each dimension whether the node’s costs and benefits depend on the technology used to enter it

ordered list, contains values for different dimensions

ordered list, holds degree (calculated from limits and payoffs) for a long time range

ordered list, holds degree (calculated from limits and payoffs) for a short time range

holds the nodes history (everything that may change in length and thus cannot be used with stats-extension)

integer, node-id allows to adress all nodes p.e.

integer, lifetime of a node, node dies if lifetime becomes zero.

ordered list, holds limits for a short time range, each dimension may have an upper and a lower limit, “don’t care” indicated by “e”, Euler’s number

ordered list, holds limits for a short time range, each dimension may have an upper and a lower limit, “don’t care” indicated by “e”, Euler’s number

string, indicating the semantic type of node

bool, true if too much agents (see short-time-limits, first dimension “capacity”) are on the node

ordered list, represents the actual values of the node (different dimension), calculated by use of costs-benefits-nodes and usage of the node by agents.

ordered list, represents the actual values of the node (different dimension), calculated by use of costs-benefits-nodes and usage of the node by agents.

ordered list, represents the actual values of the node (different dimension), calculated by use of costs-benefits-nodes and usage of the node by agents.

list, containing pairs of technology->technology-name/technology-type->technology-type-name and bool, indicating wether technologies with the same technology->technology-name may be used on the node.

how often were control-factor-values decreased?

how often were control-factor-values increased?

holds past values of degree-values

how often were technologies re-allowed?

how often were technologies banned?

ordered list of integers, indicating standard deviation of node-type-costs-benefits-agent-mean values.

ordered list of integers, holds mean costs and benefits values for each dimension, to be used to alter the agent’s payoff caused by by the agent himself entering the node.

ordered list of integers, indicating standard deviation of node-type-costs-benefits-external-mean values.

ordered list of integers, holds mean costs and benefits values for each dimension, to be used to alter external payoff caused by an agent entering the node.

ordered list of integers, indicating standard deviation of node-type-costs-benefits-nodes-mean values.

ordered list of integers, holds mean costs and benefits values for each dimension, to be used to alter the node’s payoff caused by an agent entering the node.”

vector, indicating for each dimension whether the node’s costs and benefits depend on the technology used to enter it.

integer, deviation value (of normal distribution) of this type’s lifetime

integer, mean value (of normal distribution) of this node-type’s lifetime

ordered list of integers, holds limits for a long time range, each dimension may have an upper and a lower limit, “don’t care” indicated by “e”, Euler’s number

ordered list of integers, holds limits for a short time range, each dimension may have an upper and a lower limit, “don’t care” indicated by “e”, Euler’s number

string, indicating the node-type’s name, used to instantiate nodes later on.

list of strings, names of technologies allowed to enter the node that will be instantiated based on the given node-type

if scenario is given by different .txt-files, this variable holds the node-file

used for evaluation purposes

integer, holds the number of dimensions, the present scenario consists of.

string, indicating which level of information shall be used by “out” function

int, indicating which agent shall be used for inspection in full SimCo

bool, shall “out” output be printed?

nested table, holds functions to calculate p-values for nodes/edges of an action for each goal agents try to pursue, indicated by index of goal

if scenario is given by different .txt-files, this variable holds the fle specifying functions used to calculate p-values within seu-calculation.

payoffs on edges calculated per tick if “true”, default false

payoffs on nodes calculated per tick if “true”, default false

GUI variable, used in automated-control

GUI variable, used in automated-control

bool,

table, holds names of all output-file-names to be used when exporting results.

this.resultsPath

The relative path from the current HTML page to the results page directory.

not used actually?

int, used to set seed-value before loading experiments in order to generate replicable runs (if wished).

agents shall choose from those actions, whichs SEU value is above seu-fuzzy-factor * best-seu-value.

list if mean seu values, indicating how far agents of each type reached their individually rated goals with the recent decision taken.

used for seu-output, will be true after header of seu-output-file was written.

int, used to change some seu-values for calibration purposes, indicates the set of numbers to be altered.

if scenario is given by different .txt-files, this variable holds the file specifying seu-variables

length (in ticks) fo short-time period.

switches true/false everytime the show-agents button in GUI is pressed.

bool, indicating whether the user actually runs simco-simple.nlogo or simco.nlogo (important for exporting plots, for example).

contains standard setup file, may be used in manual and automated mode.

hold global statistic values, using stats extension of netlogo.

if scenario is given by different .txt-files, this variable holds the technologies-file

bool.

used to calculate edge-delay for agents who uses the technology by multiplication.

used to calculate costs and benefits, by map-multiplication with cost-benefits-vectors of nodes/edges within calculate-costs-benefits

the individual ID of the technology.

technology will be unusable when time is passed (starts at the moment an agent purchases the technology, value decreased each tick)

bool, indicating whether technologies’ lifetimes shall be randomized (with value from input file as maximum number).

links the corresponding technology-type-object

the technologie’s name.

the technologie’s purchase price

table, using agent-type (string) to retrieve the corresponding technology-switch-condition (task, indicating wether an agent may switch

alters (by multiplication)

alters (by multiplication) the technology-factor of all technologies with the same name, changed due to controlling interventions.

used to calculate edge-delay for agents who uses the technology instantiated based on this technology-type by multiplication.

used to calculate costs and benefits of the technologies instantiated based on this technology-type, by map-multiplication with cost-benefits-vectors of nodes/edges within calculate-costs-benefits

deviation value of the technology-type’s lifetime

mean value of the technology-type’s lifetime

the technology-type’s name

the technology-type’s purchase price

holds statistic for all technologies based on this technology-type.

vector to count the total numbers of each technology-type used.

vector to count the total numbers of each technology-type used, differentiated by agentType.

vector to count the fraction of each technology-type used differentiated by agentType.

vector to count the the sum of fraction of each technology-type used differentiated by agentType.

vector to count the fraction of each technology-type used.

weighting of goals for different types of agents.

bool, shall the standard scenario format “snf” be used?

dimension to view

string, name of view

string, time horizon: “short” or “long”, indicating which set of limits/degrees shall be used for visualization