Identify#
- class hybrid_aif.composition.Identify[source]#
Bases:
NamedTupleTwo parameter variables identified as one, or an out-port identified with an in-port.
Ports.
aandbname 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’sSystem.observesgains(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_namesentryNone), so no planner chooses it; ajoint_planner()collapses it into the driver’s node. Undercouple()the two ports lie in different components.Parameter variables.
aandbname entries of the composite’sparameters("rover.field","mission.field": a component’s own parameter name under its prefix). The composite keeps one variable undera, witha’s declaration (its prior and its counts), and every state factor, modality or emission that readbreadsa. The two must be the same family with the same table shape; anything else raises, naming both.b’s counts are discarded: onlya’s declaration survives, so identify beforeb’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 bystats, the counts since the last report, andmodeandsampleof a parameter stay deferred. Design: nesting-and-coupling.md N2, N6.- static __new__(_cls, a, b)#
Create new instance of Identify(a, b)