joint_planner

Contents

joint_planner#

hybrid_aif.composition.joint_planner(system, params, node=None, *, inputs=None, **config)[source]#

The planning problem of node of a merged or coupled System, as one mind.

node is the name of a component that is not a leaf (a merged component, or a component of a coupling that is itself composed); None is the whole System. The result is a (System, SystemParams) of the node’s slots and variables whose faces plan every control node of the node jointly; the module docstring describes what it holds.

config overrides the configuration: any of policy_len, planner, gamma, num_iters, decomposition, planning_belief, feedback, mixture_schedule, mixture_k, epistemic and terms. A field not given is the composite’s value where it states one (the whole System’s own; a nested node is the composite being planned, and a field stated on an enclosing composite does not reach into it), else the value every leaf of the node declares; leaves that differ are refused. UNSET is refused as an argument. The composite’s own habit, precision, durations and scoring, where it states them, are authoritative; otherwise they are composed from the leaves’ records.

inputs as in subsystem(): for a nested node, the level at which a control node driven from outside the node is held (a driven node whose driver is inside the node is collapsed and takes no input).

Refused with a sentence: a System that is not composed, a node that is a leaf, leaves that differ on a configuration field, scoring declared by two leaves, durations on two nodes (a round has one clock) or on a node a collapse removes, precision declared by some leaves and not others or with different values, a habit that does not join (a policy module, a continuous node, a leaf whose own policy set the joint view does not have), an actuator kernel on the action node of a collapsed pair, and a collapse that makes a state factor read one node twice.