Mesoscope bad frames QC datasets incorrect

[k1o0]

There is a bug in the way the 'badframes' / 'exptQC' arrays are being read by the suite2p task. The reason for my suspicion is that in at least one session (SP035\2023-03-01\001) the original mat files (concatenated) don't correspond to the alf files that are output.
[...]
there are 3 consecutive bouts here. Could it be that the concatenation of the data is done in the wrong order? It looks to me like the resulting output is [2,1,0] rather than [0,1,2]?
[...]
If this is indeed the case this needs to be resolved asap and all suite2p tasks with >1 imaging bout need to be re-run. Right now the QC + badframes reported by the experimenter are not actually being taken into account for ROI detection in suite2p, so the ROIs can't be trusted. In fact I only looked into this because the ROIs in this particular session looked weird...