Functional GUI Requirements

Initial Ideas

• 2D world map with product footprints overlayed on hi-res land-cover surface, 3D would be nice

Input and Output Files

• Dedop processor shall only accept Sentinel-3 L1A as input files. L1A files contain geo-located bursts with all calibrations applied.

• Dedop processor shall generate Sentinel-3 L1B and (optional) Sentinel-3 L1B-S. L1B files contain geo-located and fully calibrated multi-looked SAR power echoes. L1B-S files (which is an intermediate product) contain fully SAR-processed and calibrated SAR echoes, arranged in stacks prior to multi-looking.

The format of these files is netCDF and is specified in the document "Product Data Format Specification - SRAL/MWR Level 1 & 2 Instrument Products", issue 2.0.

Other auxiliary input files, in JSON format, are:

• Characterisation file (CHD): containing parameters related with the instrument.

• Configuration file (CNF): containing parameters that modify the processing, such as switches.

• Constants file (CST): containing basic constants.

• Dedop processor shall use CHD, CNF and CST files.

• Dedop GUI shall allow the user to modify the Configuration (CNF) parameters.

GUI/Processor Options (TBC)

1. Configurations

• Users are able to save and load configurations.
• Users can reset CNF, CHD, CST to default values.
• Users can choose among default configuration scenarios.
• Configuration fields can be labeled as "beginner" or "advanced".

2. Processing

• Users can process a defined range of input, e.g.: the first 100 records, or a region of interest.

3. Breakpoints

• Users can pause the processing at predefined locations (e.g. before or after some algorithms).
• Users can then view the values of a set of variables.
• Users can store intermediate plots or data files.

4. Plug-ins

• Plug-ins allow to override the default behaviour of some modules.
• Plug-ins can be dynamically discovered.