Project: datamanagement
Issue DM-4836: Fix logic for applying aperture corrections
With the current flow, the aperture corrections are being applied only after all the measurement plugins have run through, independent of their execution order. This results in plugins whose measurements rely on aperture corrected fluxes (i.e. with execution order > APCORR_ORDER) being applied prior to the aperture correction, leading to erroneous results. The only plugin currently affected by this is {{base_ClassificationExtendedness}}. This ticket involves applying a temporary fix to ensure proper application and order of aperture corrections. However, the problem highlights the fact that the current logic of how and when aperture corrections are applied should be reworked (on another ticket) to be less error-prone.
Story points: 6