When selecting the applicable Configured Processor for a processing order, the processing mode must be taken into account. Currently the processing mode is only available in the "Processing_Mode" dynamic parameter, which is specific to S5P (and is cumbersome to search for).
Therefore a "mode" attribute shall be added to the Configuration class, the values of which are restricted to the modes defined for the respective mission.
Note that this does not make the "Processing_Mode" dynamic parameter obsolete: Since this parameter is mission-specific, no generic approach can ensure that it is set properly (or at all).
Workaround: During planning check for "Processing_Mode" dynamic parameter (if not set, a Configuration is valid for all modes; equivalent to the future "mode" parameter being set to null). This at least works for Sentinel-5P.
When selecting the applicable Configured Processor for a processing order, the processing mode must be taken into account. Currently the processing mode is only available in the "Processing_Mode" dynamic parameter, which is specific to S5P (and is cumbersome to search for).
Therefore a "mode" attribute shall be added to the Configuration class, the values of which are restricted to the modes defined for the respective mission.
Note that this does not make the "Processing_Mode" dynamic parameter obsolete: Since this parameter is mission-specific, no generic approach can ensure that it is set properly (or at all).
Workaround: During planning check for "Processing_Mode" dynamic parameter (if not set, a Configuration is valid for all modes; equivalent to the future "mode" parameter being set to null). This at least works for Sentinel-5P.