Fix wrong assert in muon decoding

small fix for a problem found during monitoring

added RTA label

mentioned in issue #323 (closed)

Thanks @satta . Do you understand why this was happening infrequently (at least I could not see a pattern)? Given that we were running with emulation, I would have expected it to happen either all the time, or never.

In the regions where strip crossing must be done (in code alreadyPads=false) a std::bitset<500> used is created. It has been dimensioned as the maximum number of strips in a quarter of a muon region. Such number is 480. The assert is simply checking that the digits (i.e. strips) number is in each event is below such number.The bug was simply that such check was exteded also in the region where the crossing is not needed. In such region the limit of 480 can be exceeded but the vector std::bitset<500> is not used so the assert is not needed.

/ci-test

assigned to @rmatev

added ci-test-triggered label

• [2023-08-20 23:34] Validation started with lhcb-master-mr#8964

resolved all threads

added Muon cleanup labels

merged

mentioned in commit 256a7830

changed title from Muon decoding bug fix to Fix wrong assert in muon decoding

mentioned in issue Moore#652 (closed)