The CI would only detect a deviation from the normalized value based on a configurable threshold, typically 1.25 (so we would tolerate a 25% increase). However, it often happens that a timing gets shorter (e.g., forgot to put the timing measurements). This commit introduces a "Deviation Threshold" (smaller than 1) to not only check that we exceed 1.0 + "Deviation Threshold" (as before), but also that are not below 1.0 - "Deviation Threshold". In other words, assuming a maximum divergence of 25%, instead of just checking if val > 1.25, we now also check if val < 0.75 (and flag error).
37 lines
945 B
YAML
37 lines
945 B
YAML
#this is a configuration file
|
|
#used to build real time processing statistics
|
|
#for 5G NR phy test (gNB terminate)
|
|
Title : Processing Time (us)
|
|
ColNames :
|
|
- Metric
|
|
- Average; Max; Count
|
|
- Average vs Reference Deviation (Reference Value; Acceptability Deviation Threshold)
|
|
Ref :
|
|
feprx : 120.0
|
|
feptx_prec : 30.0
|
|
feptx_ofdm : 50.0
|
|
feptx_total : 120.0
|
|
L1 Tx processing : 300.0
|
|
DLSCH encoding : 230.0
|
|
L1 Rx processing : 175.0
|
|
PUSCH inner-receiver : 100.0
|
|
PUSCH decoding : 180.0
|
|
Schedule Response : 111.0
|
|
DL & UL scheduling timing : 37.0
|
|
UL Indication : 3.0
|
|
Slot Indication : 38.0
|
|
DeviationThreshold :
|
|
feprx : 0.25
|
|
feptx_prec : 0.25
|
|
feptx_ofdm : 0.25
|
|
feptx_total : 0.25
|
|
L1 Tx processing : 0.25
|
|
DLSCH encoding : 0.25
|
|
L1 Rx processing : 0.25
|
|
PUSCH inner-receiver : 0.25
|
|
PUSCH decoding : 0.25
|
|
Schedule Response : 0.25
|
|
DL & UL scheduling timing : 0.25
|
|
UL Indication : 0.25
|
|
Slot Indication : 0.25
|