REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

Error while checking build/O2/fullCI_slc9 for 01a6a32 at 2026-03-02 23:36:

## sw/BUILD/O2Physics-latest/log
c++: fatal error: Killed signal terminated program cc1plus
ninja: build stopped: subcommand failed.


## sw/BUILD/o2checkcode-latest/log
--
========== List of errors found ==========
++ GRERR=0
++ grep -v clang-diagnostic-error error-log.txt
++ grep ' error:'
++ GRERR=1
++ [[ 1 == 0 ]]
++ mkdir -p /sw/INSTALLROOT/aa9b3f35ca0fd74682683a24a8b1ad4e500ce95d/slc9_x86-64/o2checkcode/1.0-local100/etc/modulefiles
++ cat
--

Full log here.

Hi @AizatDaribayeva, @njacazio, a comment from my side: I see that this PR modifies how the retrieval of the alpha angle and of the X of a given ML/OT sensor, i.e. by subtracting the number of VD modules.
What is done, to me, seems now consistent to how the mCacheRefXMLOT are filled (starting from 0 and not from getNumberOfActivePartsVD. Anyway, I'm worried that there could still be an inconsistency on how that array is used, in the TimeFrame class.
See in particular:

Ah I see that the PR was just merged in the meantime, but let's anyway have a look at this point, thanks

Ciao @fcolamar we can revert if needed

Actually re-checking it should be fine, in the getSensorRefAlphaMLOT there's indeed the subtraction by getNumberOfActivePartsVD that brings back the chip value passed as argument to 0 for the first ML module.
All clear, thanks!