Executing a multinode model is executing its nodes in a model instance scope.
qsmm_node_call_default starts executing a node.
An executed node can call other nodes or finish its own execution causing that function to return control.
Executed nodes use a call stack similar to a function call stack.
The frames of this stack can contain application-specific information usable in event handler functions.
The execution of a node consists of a series of assembler instruction invocations for the changing current state of this node. The event handler of an instruction meta-class processes the invocations of assembler instructions belonging to instruction classes derived from this instruction meta-class. An invoked instruction returns an outcome the environment state identification engine uses to select the next node state.
As a side effect of processing an instruction invocation, the event handler of an instruction meta-class can increment continuous time, change spur tracked by the environment state identification engine or instruction emitting engine, or modify look-ahead signals taking part in the selection of next node state. If the multinode model operates correctly, the state models of executed nodes are adapting to provide higher spur increment velocity.
To evaluate whether a model provides adaptive behavior, a developer can compare the efficiency of this model in adaptive mode of operation with the efficiency in random mode of operation.
|• Incrementing Time and Spur|
|• Transferring Control between Nodes|
|• Handling Instruction Invocation|
|• Setting Look-ahead Signals|
|• Setting Instruction Classes Weights|
|• Working with the Node Call Stack|
|• Switching Adaptive or Random Behavior of a Multinode Model|
|• Tracing Model Execution|