flepimop2-op_system

flepimop2-op_system provides the flepimop2 system adapter for op_system.

It packages the flepimop2.system.op_system provider so flepimop2 can load and execute RHS specifications compiled by the core op_system package.

Bound system steppers accept and return Flepimop2's backend-neutral Array protocol. The provider performs no state conversion: NumPy, JAX, and other supported namespaces are selected by the state supplied by the engine.

System options preserve normalized axis metadata for engine providers: axis_order, axis_sizes, numeric axis_coords, original axis_labels, and declared axis_types. Consumers can therefore distinguish categorical, ordinal, and continuous semantics without inferring them from coordinate values.

It also provides the sparse_table parameter module, which assembles a dense array for a routing transition's matrix parameter (for example eta[time, imm:i, imm:j]) from a declared support. Each entry is a number or any nested parameter configuration, sampled with the request's leading axes:

parameter:
  eta:
    module: sparse_table
    indices: [imm, imm]
    entries:
      - index: [x0, x3]
        value: {module: fixed, value: 0.2}
      - index: [x5, x7]
        value: 1.0

Off-support entries are zero. SparseTableParameter.support(axes) returns the support positions for inference.