#range #numeric #quantization #bandwidth #numbers #save #smaller

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

#4 in #bandwidth

Download history 1121/week @ 2024-08-28 750/week @ 2024-09-04 462/week @ 2024-09-11 342/week @ 2024-09-18 337/week @ 2024-09-25 294/week @ 2024-10-02 214/week @ 2024-10-09 356/week @ 2024-10-16 332/week @ 2024-10-23 131/week @ 2024-10-30 188/week @ 2024-11-06 210/week @ 2024-11-13 268/week @ 2024-11-20 276/week @ 2024-11-27 309/week @ 2024-12-04 203/week @ 2024-12-11

1,099 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

~160KB