Right now, only oneFunctionData field can be a pint.Quantity. It would be useful for the entire cost function API to be compatible with Pint units, including all FunctionData fields.
To go one step further, we might even validate the units of the FunctionData fields in relation to each other: for instance, for QuadraticFunctionData, there must exist some units Y and X such that constant_term has units Y, proportional_term has units Y/X, and quadratic_term has units Y/X^2. This is less important though.
Right now, only one
FunctionDatafield can be apint.Quantity. It would be useful for the entire cost function API to be compatible with Pint units, including allFunctionDatafields.To go one step further, we might even validate the units of the
FunctionDatafields in relation to each other: for instance, forQuadraticFunctionData, there must exist some units Y and X such thatconstant_termhas units Y,proportional_termhas units Y/X, andquadratic_termhas units Y/X^2. This is less important though.