When the transition for meas_algorithms to meas_base was originally done, part of Jim's spec was to change the order of arguments in the run() method of SingleFrameMeasurementTask. But since we wanted the meas_algorithms framework to continue to work, we decided to temporarily allow both argument orders,
DM-3804, we are now going to allow only the run(measCat, exposure).
I intend to track down any contrary instances of this call in the stack, but I may miss things in private code or code outside of the main pipeline. Please inform me of any code which uses the sfm.run(exposure, measCat) ordering so I can fix it during this change.