Wearable sports sensors can recognize actions on the device itself, where lower-precision numbers reduce model storage and memory traffic. Two 4-bit block-scaled formats, MXFP4 from the Open Compute Project, introduced in 2023, and NVFP4 from NVIDIA, introduced in 2025, are drawing interest. Published evaluations cover general deep-learning benchmarks and large language models; to our knowledge, nobody has yet measured what they cost a small wearable-sensor model. We train a 159,492-parameter 1D CNN to recognize four basketball actions from wrist-accelerometer data in Hang-Time HAR and test it on players it has never seen, using five-fold cross-validation grouped by player. Every comparison between number formats is made fold by fold. In full precision the model reaches 69.26% macro-F1. Measured TFLite FP16 and INT8 models lose at most 0.16 percentage points. In simulation, 4-bit weights cost 1.45 points with MXFP4 and 0.72 points with NVFP4. When activations are quantized to 4 bits as well, MXFP4 loses 5.14 points and NVFP4 only 0.75, and NVFP4 comes out ahead in all five held-out-player folds. The ranking survives two alternative simulator settings, with NVFP4 leading by 3.49 to 4.40 points. A 2×3 ablation with 4-bit weights and activations (two block sizes and three scale rules) points to scale selection as the main source of MXFP4's loss. The reference MXFP4 conversion we simulate rounds the scale down, which can pick scales that are too small, so many blocks clip their largest values. Rounding the scale up recovers 3.18 points with 32-value blocks and 3.63 points with 16-value blocks, and switching to an 8-bit floating-point scale, as NVFP4 does, adds another 0.84 and 1.20 points. Block size matters less. Under this round-down rule, 16-value blocks score 0.44 points below 32-value blocks in all five folds; under the other two rules there is no consistent effect.
Figures & tables
Version
File (KiB)
Macro-F1
Δ vs. FP32 (folds lower)
Same answer as FP32 (%)
p50 latency (ms)
FP32
630.9
0.6926 ± 0.0494
0 (identical)
100.00
0.0867
FP16
323.8
0.6925 ± 0.0494
− 0.0001 (3/5 lower)
99.99
0.0866
INT8, dynamic range
181.0
0.6924 ± 0.0494
− 0.0003 (3/5 lower)
99.81
0.0807
INT8, full integer
182.8
0.6910 ± 0.0495
− 0.0016 (5/5 lower)
98.68
0.0865
Table 1: Deployable TFLite versions ( measured ). Macro-F1 is mean ± sd over 5 player-grouped folds. Δ is the paired mean difference from FP32, with the number of folds in which the version scored lower. Latency: median of 5 interleaved rounds of 2,000 single-window runs, 1 thread, on a Google Colab CPU virtual machine (VM; Intel Xeon @ 2.20 GHz, KVM, 2 vCPUs = 1 core × 2 threads; Ubuntu 24.04.5; Python 3.13.16; TensorFlow 2.21.0). Latencies of the same files differed by 11.6–24.6% between two Colab sessions, so these differences are within noise.
Weights only (W4 / W8)
Weights + activations (W4A4 / W8A8)
Format
Bits/weight
Weights KiB
Macro-F1
Δ (folds lower)
Macro-F1
Δ (folds lower)
INT8
8.12
165.0
0.6928
+ 0.0002 (1/5)
0.6930
+ 0.0004 (2/5)
INT4
4.12
88.2
0.6921
− 0.0006 (2/5)
0.5493
− 0.1433 (5/5)
MXFP4
4.25
90.8
0.6782
− 0.0145 (5/5)
0.6412
− 0.0514 (5/5)
NVFP4
4.50
95.6
0.6854
− 0.0072 (5/5)
0.6851
− 0.0075 (4/5)
Table 2: Simulated formats (fake quantization; no speed or energy). Bits/weight include scale storage: per-channel FP32 scales for INT8 and INT4, block scales for the FP4 formats, and NVFP4’s FP32 tensor scale. Weights KiB is calculated for the quantized kernels plus FP32 biases and batch-normalization parameters. Δ is the paired mean difference from FP32 (0.6926), with the number of folds (of 5) in which the format scored lower. INT4 and INT8 use one scale per window for activations, so their W4A4/W8A8 rows are not like-for-like with the blocked FP4 formats.
Figure 1: Change in macro-F1 from FP32 for every fold (markers) and the mean of the 5 folds (black line), simulated . The text above each group gives the number of folds (groups of test players) in which that format scored lower than FP32. Fold 4 (red) accounts for most of MXFP4’s mean loss. Open markers: INT4 W4A4 uses one activation scale per window and is not like-for-like with the blocked FP4 formats. n=5 folds; the same 5 trained models throughout.
Block
E8M0 down
E8M0 up
E4M3 + tensor
32
− 0.0145 / − 0.0514
− 0.0063 / − 0.0196
− 0.0080 / − 0.0112
16
− 0.0167 / − 0.0558
− 0.0073 / − 0.0195
− 0.0072 / − 0.0075
Table 3: Ablation study ( simulated ): mean change in macro-F1 from FP32, weights only / weights + activations. MXFP4 = block 32 with E8M0 rounded down; NVFP4 = block 16 with E4M3.
Figure 2: Ablation study, W4A4, simulated : per-fold change in macro-F1 from each design step (markers; fold 4 red; black line = mean of 5 folds). B is the block size. The text above each group gives the number of folds in which the step helped or hurt. Rounding the E8M0 scale up gives most of the gain; an E4M3 scale adds a smaller, also consistent, gain. Under the MX rule (E8M0 rounded down), 16-value blocks are slightly worse than 32-value blocks.
Variant
MXFP4
NVFP4
NVFP4 − MXFP4
Main
− 0.0514 (5/5)
− 0.0075 (4/5)
+ 0.0439 (5/5)
Ties to even
− 0.0514 (5/5)
− 0.0075 (4/5)
+ 0.0440 (5/5)
Layer-1 patch blocks
− 0.0444 (5/5)
− 0.0095 (5/5)
+ 0.0349 (5/5)
Table 4: Sensitivity of W4A4 results ( simulated ). Change in macro-F1 from FP32, with folds lower (of 5); last column: NVFP4 minus MXFP4, with folds in which NVFP4 is higher. Main: the notebook’s definitions (ties to smaller; one layer-1 activation block per time step).