- 22 May, 2024 40 commits
-
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
Jaroslava Fiedlerova authored
- Enable build of T2 lib in RAN-gNB-N300-Timing-Phytest-LDPC - Add testcases with 2 layers
-
Jaroslava Fiedlerova authored
Add ulsch decoding measurements, which are reported by nr_ulsim. Start ulsch_decoding_stats measurement before nr_ulsch_decoding is called and stop it after collection of all decoder tasks from Tpool. In the context of nr_ulsim, ULSCH_id is allways == 0, testing is performed per one TB, therefore measurement is started and stopped only once per trial. Reported ulsch decoding statistics show the mean ulsch decoding time over x trials (specified by -n command line option of nr_ulsim). This measurement does not provide valid information in case of nr-softmodem, when the loop is done over multiple ULSCH IDs - start of the measurement is done multiple times and stops only once in this case. For unitary physical simulators, ULSCH processing loop is executed only once - the max number of PUSCH is set to 1. This ensures exactly one start and stop of the ULSCH decoding time measurement per processed TB. Note: ulsch decoding statistics reports average time of segmentation, rate matching, interleaving and decoding of the TB
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
- Enable both nr_ulsim and nr_dlsim test with Run_T2Test - Introduce time threshold variable for T2/CPU LDPC tests - Set threshold individually for each test - T2 encoding/decoding and CPU encoding/decoding - Check if encoder/decoder processing time is below the threshold - Remove NOK return option - keep only OK (processing time below threshold) or KO (proceesing time beyond threshold) - Rename function to run and check results of CUDA ldpctest - Use new SSH class in function for check T2 test results, use f-strings
-
Jaroslava Fiedlerova authored
- Modify T2 PCI adr for CI T2 test setup - Set PKG_CONFIG_PATH env var manually if needed (DPDK lib installed into custom path)
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
Simplification of the code by replacing iperf_opt by target_bitrate (returned from Iperf_ComputeModifiedBW) - no need to repeat the steps to retrieve information about requested bitrate from iperf_opt. Compute iperf bitrate performance as receiver bitrate over requested (target) bitrate. Fix an issue with misdetection of missing report line - "result" was defined 2x in the function. With this MR, result can be only None or stores output of re.search() for matching the report line pattern, which ensure proper detection of the report line as well as presence off all required components in the report line.
-
Jaroslava Fiedlerova authored
Sender bitrate is not always equal to the requested bitrate (set by "-b" iperf option) in iperf3 (v3.9) UDP tests, so we have to compture bitrate performance of UDP iperf3 test as receiver over requested bitrate. Bitrate performance then express percentage of requested bitrate, which is received on the receiver side.
-
Jaroslava Fiedlerova authored
For iperf3 (version 3.9) UDP, sender bitrate is not always equal to requested bitrate (defined by '-b' option). We need to retrieve information about the requsted bitrate from iperf command line options specified for each UDP testcase. This parameter is then used in UDP analysis functions for proper evaluation of the test results.
-
Teodora authored
-
Teodora authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Raymond Knopp authored
fixes the overflow issue in the PUCCH2 RX with 4+ RX antennas and 12+ bits (polar code format). The fix scales the polar decoding LLR computation according to the number of RX antennas. The issue was clear for 100 MHz 4 RX antennas. Even nr_pucchsim -s -5 -q 8 -P 2 -b 12 -R 273 -z4 -n1000 doesn't converge to 0 BLER with increasing SNR. The issue didn't appear in CI because of the bandwidth and antenna count limitations.
-
Raphael Defosseux authored
Signed-off-by:
Raphael Defosseux <raphael.defosseux@eurecom.fr>
-
Laurent THOMAS authored
-
Laurent THOMAS authored
-
Robert Schmidt authored
Prior to this commit, it might happen that the gNB used TDA 0 (Start 0 len 13) for mixed slot, in which case the UE could not send msg3 (because a mixed slot has less than 13 symbols).
-
Robert Schmidt authored
- It is only a couple of bytes - It hid a bug: if two preambles, L1_nr_prach_procedures() overwrote the preamble of the first with the second one
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
if we reduce, we will never do all rach indications. Go one-by-one instead.
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-