@scottpurdy "I don't understand why the typecast function is needed. The base encoder knows the type so shouldn't the vector encoder just wrap and unwrap the values with a list/vector?"

I think it would work for "other data types" (such as strings, ...) but the most common ScalarEncoder internally represents data as floats, and then tests (and real use-cases) would fail on [1 2 3] != [1.0 2.0 3.0]

the "OPF format" of the line above outputs: `({'[1:3]': ([[3.0, 3.0]], '3.00')}, ['[1:3]'])` which I recall to be: "name: [[values_as_scalar, orig_value]], 'value as string' [sth?]"