L2 Normalization Prototype and Function List¶
Description¶
This kernel normalizes data across the specified dimension using L2 norm according to the following formula:
Where:
\(x_{i}-i_{th}\) - value in input data subset
\(x_{j}-j_{th}\) - value in the same input data subset
\(y_{i}-i_{th}\) - value in output data subset
\(epsilon\) - lower bound to prevent division on zero
Note
epsilon tensor currently isn’t used in integer-based versions of the kernel (fx16, sa8)
and is preserved only for possible future use.
L2 normalization function might be applied to the whole tensor, or along a specific axis. In the first case all input values are involved in the calculation of each output value. If the axis is specified, then the function is applied to each slice along the specific axis independently.
This kernel uses a look-up table (LUTs) to perform data transformation. See Look-Up Tables (LUT) Manipulation Prototypes and Function List section and the pseudo-code sample for more details on LUT structure preparation. Use the following functions for the purpose:
mli_krn_l2_normalize_get_lut_size
mli_krn_l2_normalize_create_lut
Functions¶
Kernels which implement L2 normalization functions have the following prototype:
mli_status mli_krn_l2_normalize_<data_format>(
const mli_tensor *in,
const mli_tensor *epsilon,
const mli_lut *lut,
const mli_l2_normalize_cfg *cfg,
mli_tensor *out);
where data_format is one of the data formats listed in Table MLI Data Formats and the function
parameters are shown in the following table:
Parameter |
Type |
Description |
|---|---|---|
|
|
[IN] Pointer to constant input tensor. |
|
|
[IN] For future use. Pointer to tensor with epsilon value. |
|
|
[IN] Pointer to a valid LUT table structure prepared for L2 normalization. |
|
|
[IN] Pointer to L2 Normalize parameters structure. |
|
|
[IN | OUT] Pointer to output tensor. Result is stored here |
mli_l2_normalize_cfg is defined as:
typedef mli_prelu_cfg mli_l2_normalize_cfg;
See Table mli_prelu_cfg Structure Field Description for more details.
Function Name |
Details |
|---|---|
|
All tensors data format: sa8 |
|
All tensors data format: fx16 |
Conditions¶
Ensure that you satisfy the following general conditions before calling the function:
inandouttensors must be valid (see mli_tensor Structure Field Descriptions) and satisfy data requirements of the selected version of the kernel.
epsilontensor isn’t used and can be passed as aNULLpointer or other value.
inandouttensors must be of the same shapes.
lutstructure must be valid and prepared for the L2 Normalization activation function (see Look-Up Tables (LUT) Manipulation Prototypes and Function List).
mem_strideof the innermost dimension must be equal to 1 for all the tensors.
axisparameter ofcfgstructure might be negative and must be less thanintensor rank.
For sa8 versions of kernel, in addition to general conditions, ensure that you satisfy the following quantization conditions before calling the function:
intensor must be quantized on the tensor level. This implies that the tensor contains a single scale factor and a single zero offset.Zero offset of
intensor must be within [-128, 127] range.
Ensure that you satisfy the platform-specific conditions in addition to those listed above (see the Platform Specific Details chapter).
Result¶
These functions modify:
Memory pointed by
out.data.memfield.
el_paramsfield ofouttensor.
It is assumed that all the other fields and structures are properly populated to be used in calculations and are not modified by the kernel.
The range of this function is (-1, 1). Depending on the data type, quantization parameters of the output tensor are configured in the following way:
fx16
out.el_params.fx.frac_bitsis set to 15. Hence, the maximum representable value of L2 normalization is equivalent to 0.999969482421875 (not 1.0).sa8
out.el_params.sa.zero_point.mem.i16is set to 0
out.el_params.sa.scale.mem.i16is set to 1
out.el_params.sa.scale_frac_bits.mem.i8is set to 7
The kernel supports in-place computation. It means that out and in tensor structures
can point to the same memory with the same memory strides but without shift.
It can affect performance for some platforms.
Warning
Only an exact overlap of starting address and memory stride of the in and out
tensors is acceptable. Partial overlaps result in undefined behavior.
Depending on the debug level (see section Error Codes) this function performs a parameter
check and returns the result as an mli_status code as described in section Kernel Specific Configuration Structures.