The types an inference backend shares, so calling code names a backend once rather than at every call site. `API.Onnx` runs a model in-process; `API.Inference` sends it to a server. They answer the same question and neither is right for every deployment: ONNX needs a model file and a runtime for the architecture, a server is the only GPU path today, and a model that will not convert to ONNX reaches Objeck no other way (docs/INFERENCE_ENGINES_PLAN.md). This bundle exists because both previously defined their own `Tensor`. That was deliberate and temporary -- the generic ONNX run shipped before a shared library existed -- and two near-identical classes drift. They are one class now. Compile with -lib models.
TensorSpec
One input or output in a model's signature: its name, element type and shape. A dimension a model leaves symbolic -- a batch size, a sequence length -- is reported as -1. That is not a gap in the report: the model genuinely does not fix it, and only the caller can.
Operations
GetDatatype #
The element type the model declares, e.g. "FP32", "INT64".
method : public : GetDatatype() ~ StringReturn
| Type | Description |
|---|---|
| String | element type name |
GetName #
The name to use for this tensor in a run.
method : public : GetName() ~ StringReturn
| Type | Description |
|---|---|
| String | name |