write_back

Contents

write_back#

hybrid_aif.composition.write_back(composite, params, name, before, after)[source]#

params with the parameter variables the view of name learned set to after’s.

before is the view’s params as subsystem() returned them and after the same view’s params after learning. Each variable before holds must equal the composite’s current entry (same type, shape and values, compared concretely) and is then replaced by after’s, so the composite holds exactly what the view learned, decay included. A stale before raises: take the view again from the composite after any write-back. Evidence that several views gather at once is accumulated by learning on the composite, not by writing views back. An after missing a variable before holds, a before of another shape or type, and a concentration in after that is not positive all raise. Nothing else is written: a view’s own tables are its own to carry. Bookkeeping of one home between the views of one particle; nothing writes another particle’s parameters. Design: nesting-and-coupling.md N4, N6.