Project: datamanagement
Issue DM-3183: CalibrateTask instantiates some subtasks with the wrong schema
CalibrateTask instantiates some subtasks with the wrong schema, in particular: - astrometry is instantiated with the final schema but run on schema1 - measureApCorr, applyApCorr and photocal are instantiated with schema1 but run on the final schema One way this can cause problems is that schema1 may not have the data needed to measure aperture correction (e.g. it may contain only one tiny radius of aperture flux), as came to light when running the lsst stack demo.
Story points: 1