Protect the muon decoding from unexpected data

Currently the decoding throws exceptions when a raw bank doesn't look as expected. These are replaced with error counters, and processing of the rest of the raw banks continues.

In addition, some assumptions (that seem to be violated with the current data) are now checked, preventing SIGABRT (invalid subspan arguments).

Adresses #242 but there are most certainly more issues as infrequent SIGABRT happens still in the MuonMon task.

/cc @samarian @mstahl

added Decoding Muon enhancement labels

requested review from @dbrundu and @satta

assigned to @rmatev

added RTA label

added 1 commit

• f103b820 - Protect the muon decoding from unexpected data

Compare with previous version

mentioned in issue #242

@rmatev thanks for this! Would it be possible to open an analogous request for Allen, or is that not necessary because of how Allen implements its decoding? In general we should from now on fix decoding issues simultaneously for HLT1 and HLT2.

mentioned in issue Moore#467 (closed)

added 3 commits

• f103b820...55e83324 - 2 commits from branch master
• 00f667ac - Protect the muon decoding from unexpected data

Compare with previous version

mentioned in issue Moore#474 (closed)

mentioned in merge request Allen!984 (merged)

mentioned in issue Moore#478 (closed)

mentioned in issue Moore#482 (closed)

mentioned in issue Moore#485 (closed)

added 225 commits

• 00f667ac...f534b5d9 - 223 commits from branch master
• b773fb7b - Protect the muon decoding from unexpected data
• b60fcf2a - Move checks for Tell40 integrity in a separate loop

Compare with previous version

/ci-test

added ci-test-triggered label

• [2022-10-20 15:46] Validation started with lhcb-master-mr#5980

resolved all threads

mentioned in issue #268

merged

mentioned in commit e7120b65

mentioned in issue Moore#487 (closed)