@@ -42,7 +42,6 @@ It might be required to set Clang-18 as the default clang on the machine
sudo apt install python3.13 python3.13-venv
```
## Run CUT tests on Target platform
Running the conformance tests requires around 30 gb of disk space and around 6 gb of RAM space.
@@ -97,7 +96,7 @@ CUT_OUTPUTS
+- failedCmds.txt : Log of all the shell commands that failed execution
+- dec/ : Folder containing all decoder tests CUT outputs
+- enc/ : Folder containing all encoder tests CUT outputs
+- renderer_short/ : Folder containing all renderer tests CUT outputs
+- renderer/ : Folder containing all renderer tests CUT outputs
+- split_rendering/ : Folder containing all split rendering enc/dec tests
```
@@ -105,7 +104,6 @@ CUT_OUTPUTS
If CUT test execution is done on a different platform, the scripts/CUT_OUTPUTS must be copied and provided in the reference platform's scripts/CUT_OUTPUTS. Then the BE analysis or non-BE analysis procedure below should be followed. It is recommended to perform first analysis with BE comparison and then analysis with non-BE comparison if non-BE outputs were found. Note, non-BE conformance applies currently only if metadata file output is BE and there are non-BE results only in wave-file output.
### Perform the BE comparison on the CUT outputs on reference platform
The BE comparison is performed to the CUT outputs using the command below. Encoded outputs will be decoded using the reference decoder executables as part of the process. The BE comparison is then performed between the CUT and reference decoded outputs. This includes comparison of ".wav"-files, and ".csv" and ".met" metadata files. If any non-BE results are observed, this is reported on the command-line and link to an analysis ".csv" file is given. The analysis file shows which exact files were non-BE. An example passing output is shown below. If all test sets print `PASSED BE TEST`, then CUT outputs are BE-conformant.
@@ -142,7 +140,6 @@ Analysing tests for ISAR (1252 tests)
</code></pre>
</details>
### Perform the MLD based non-BE analysis on the CUT outputs on reference platform (Ubuntu 24.04)
The non-BE analysis below compares CUT and reference outputs by running MLD on audio (`.wav`) and, when MASA metadata are generated, for the matching reference/DUT `.met` files. For encoder tests, encoded CUT bitstreams are first decoded with the reference decoder before analysis. Per-frame MLD and MASA metadata values are written to `scripts/CUT_OUTPUTS` and checked against corridor references in `testvec/testv/mld_ref` (`mld_ref_<TAG>.csv` and `masa_ref_<TAG>.csv`).
@@ -245,7 +242,6 @@ MLD Corridor passed for ISAR with max MLD diff of 0.0
</code></pre>
</details>
## Executing specific tests only
All CUT tests can be run specifically for IVAS Encoder,IVAS Decoder,IVAS Renderer, ISAR Encoder and ISAR Decoder only. The commandline allows for ```-test-mode=<PARAM>``` for this functionality, examples: