#numeric #quantization #quantize

numquant

Quantize numbers to a smaller range to save bandwidth or memory data types and back again

2 unstable releases

0.2.0 Apr 11, 2022
0.1.0 Apr 11, 2022

#16 in #quantization

Download history 221/week @ 2024-12-14 28/week @ 2024-12-21 10/week @ 2024-12-28 62/week @ 2025-01-04 142/week @ 2025-01-11 152/week @ 2025-01-18 202/week @ 2025-01-25 219/week @ 2025-02-01 188/week @ 2025-02-08 137/week @ 2025-02-15 240/week @ 2025-02-22 162/week @ 2025-03-01 122/week @ 2025-03-08 468/week @ 2025-03-15 190/week @ 2025-03-22 314/week @ 2025-03-29

1,117 downloads per month
Used in 7 crates (2 directly)

MIT/Apache

12KB
178 lines

numquant

Quantize numbers to a smaller range to save bandwidth or memory.

The input floating point value is expected within a given range. Values outside this range will be clamped. The input value will then be quantized into a given integer range.

For example, given the allowed range -1000.0 to 1000.0, and the quantized range 0 to 255 (to fit in a byte), the value -1000.0 would be quantized to 0, and 1000.0 would be quantized to 255, and values in-between are linearly interpolated between 0 and 255.

Example

This example uses the type Quantized<U8<0, 1000>> that converts any floating point number between 0.0 and 1000.0 to a byte (which has the range 0 to 255). Some precision is lost, but an approximate value can be brought back.

let original = 500.0;
// Quantize the value into a byte.
// Quantization supports inputs between 0 and 1000.
let quantized = Quantized::<U8<0, 1000>>::from_f64(original);
// Convert it back to an f64
let dequantized = quantized.to_f64();
// The conversion isn't lossless, but the dequantized value is close to the original:
approx::assert_abs_diff_eq!(original, dequantized, epsilon = U8::<0, 1000>::max_error());

Dependencies

~150KB