Multi-module detector can have differing numbers of frames for different modules

[takluyver]

@daviddoji ran into a case where one LPD module (module 11) recorded 62 frames per train, and the others recorded 60. LPD1M() can't be used if the outlier module is included, because it wants all modules to record similar data. Thankfully it checks this assumption, so there's a moderately meaningful error message: Inconsistent frame counts for train ...: {60, 62}.

This affects many (all?) runs in FXE proposal 2092. Run 185 is the example David showed me.

Workarounds:

• The LPD1M object is usable with the offending module excluded
• Get data for individual modules, slice off the extra and then stack them afterwards

For now, we are 🤞 that this is a rare misconfiguration, so we don't need to specifically accommodate it in EXtra-data. But we're noting it here so we can keep a record if it comes up more often.