In discussion with Jim Bosch, he said that the HSM moments are necessary (at minimum the HsmPsfMoments plugin, possibly all of the ones in meas_extensions_shapeHSM/config/enable.py): they're the default shape measurements, having superceded SdssShape for years. I will file a ticket to make the HSM measurements a required part of characterize (it would be nice to move that code out of meas_extensions_shapeHSM since it's not really an "extensions" thing any more, but that's a bigger question), and also re-insert the HSM stuff on this ticket and re-run.
As part of this investigation, we also discovered that characterize is almost certainly running all its plugins too many times: it only should run them after psf determination is complete, not during the determinePsf loop. This might explain why cmodel is such a large part of the runtime, if it's being run repeatedly.
In discussion with Jim Bosch, he said that the HSM moments are necessary (at minimum the HsmPsfMoments plugin, possibly all of the ones in meas_extensions_shapeHSM/config/enable.py): they're the default shape measurements, having superceded SdssShape for years. I will file a ticket to make the HSM measurements a required part of characterize (it would be nice to move that code out of meas_extensions_shapeHSM since it's not really an "extensions" thing any more, but that's a bigger question), and also re-insert the HSM stuff on this ticket and re-run.
As part of this investigation, we also discovered that characterize is almost certainly running all its plugins too many times: it only should run them after psf determination is complete, not during the determinePsf loop. This might explain why cmodel is such a large part of the runtime, if it's being run repeatedly.