Add possibility to decode v8 as v7 in the SciFi

Related to LHCb!4210 (merged), this is untested.

Data in June-July 2023 was interpreted as v7 banks, whereas the banks themselves were actually mislabelled v8. In order to reproduce this effect in MC, we introduce an option to force the decoding to version 7 even if the bank is version 8.

Solves LHCb#319 (closed)

added RTA label

I think for all the same reasons as discussed in LHCb!4210 (merged) it is not reasonable to ask the user to know when to enable, or not, the option to handle v7 as v8. If its needed then it needs to be automatic based on run number.

But then, as this is HLT1, is there actually a need to have any handling here at all ? The problem data has already been through HLT1, and its reasonable I think to assume by the time HLT1 now runs again the issue will be address in the FT firmware. Why is this option needed at all in Allen ?

resolved all threads

approved this merge request

/ci-test --platforms=x86_64_v2-centos7-clang12-opt

assigned to @rmatev

added FT workaround labels

added Decoding label

added ci-test-triggered label

• [2023-08-01 12:56] Validation started with lhcb-master-mr#8720
• [2023-09-22 23:36] Validation started with lhcb-master-mr#9290

perhaps we can also add here the opposite case (decoding v8 as v7), if everyone agrees that this is the way to run 2023 post-TS HLT1 in simulation, see LHCb#319 (comment 6975564)

changed milestone to %RTA/2023.09.01

assigned to @lohenry and unassigned @rmatev

mentioned in issue Moore#627 (closed)

mentioned in issue Moore#634 (closed)

changed milestone to %RTA/2023.09.25

added 46 commits

• 4fce3288...1d62c43a - 45 commits from branch master
• 901221e9 - Add possibility to decode v7 as v8 in the SciFi

Compare with previous version

changed title from Add possibility to decode v7 as v8 in the SciFi to Add possibility to decode v8 as v7 in the SciFi

changed the description

mentioned in issue LHCb#319 (closed)