When using CobraConfig it's usually necessary to join to mcsData purely to get the frameId. We should probably denormalise a little further (i.e. add frameId or maybe visitId), and take the opportunity to use the same name in the two tables (centroidx v. mcsCenter_x).

We might want to remove the mcs pixel coordinates from CobraConfig all together; the two tables are used for different things, and can be easily joined when investigating e.g. camera distortions.

While renaming columns it's worth thinking about using a Hungarian-style naming convention (e.g. adding including Pix in all pixel coordinates, and/or MM for all focal plane coordinates), especially when the two coordinate systems both appear in one table.

Currently both tables include information about moves (one via moveId and one via iteration. We should reconsider this too; for example, if mcsData included the nominal position in MCS pixel coordinates we might well use it for convergence analysis rather than CobraConfig; I doubt if we would use both