Identify#

class hybrid_aif.composition.Identify[source]#

Bases: NamedTuple

Two parameter variables identified as one, or an out-port identified with an in-port.

Ports. a and b name an out-port (an action node or an emission) and an in-port (a modality, or a control node), in either order. The in-port observes the out-port’s variable: the composite’s System.observes gains (in-port, out-port). An in-port is identified at most once, an out-port feeds any number, and the two port types must be equal. A control node in-port is driven: it stays in its leaf, carries the out-port’s realised value, and has no action node of its own (action_names entry None), so no planner chooses it; a joint_planner() collapses it into the driver’s node. Under couple() the two ports lie in different components.

Parameter variables.

a and b name entries of the composite’s parameters ("rover.field", "mission.field": a component’s own parameter name under its prefix). The composite keeps one variable under a, with a’s declaration (its prior and its counts), and every state factor, modality or emission that read b reads a. The two must be the same family with the same table shape; anything else raises, naming both. b’s counts are discarded: only a’s declaration survives, so identify before b’s member has learned anything worth keeping.

An identification inside one particle: the variable has one home and the readers share its counts. It is bookkeeping, not a crossing; under couple() a parameter is reported by stats, the counts since the last report, and mode and sample of a parameter stay deferred. Design: nesting-and-coupling.md N2, N6.

a: str#

A port, or the parameter variable that survives (with its declaration).

b: str#

The other port, or the parameter variable whose readers are redirected to a.

static __new__(_cls, a, b)#

Create new instance of Identify(a, b)