IPF readiness status

1. IPF readiness status • Overview of the IPF readiness status • Open items • Level 2 algorithms verification sub-group activities • Evolutions and updates mechanisms

2. Overview of the IPF readiness status • RA2/MWR IPF FAT held at the end of June: • L1b processing without problems • Good match between IPF L1b output data and L1b TDS from ref. processor (ALS) • MWR_SLT_AX and RA2_CST_AX updated in the latest TDS following MWR group suggestions • Negative Tbs coming in the TDS due to the new T_sh value in the Constants file • Original value of T_sh stored in the aux. file for the next TDS delivery before launch • The final pre-launch configuration will contain the new value

3. Overview of the IPF readiness status • L2 processing still under analysis • Discrepancies between IPF L2 output data and L2 TDS from ref. processors (CLS/MSSL)

4. Open items • Level 1b: • Some MWR SPRs raised by ALS on the ref. processor code and DPMs to be passed on to the IPF for implementation • e.g. MWR Tbs to be set to 0 if not enough number of calibration (Offset) measures in the input L0 data, warning Telemetry flags, max/min values for Tbs range checks stored in MWR_CHD_AX, etc. • Level 2: • Discrepancies between IPF processor and TDS still to be solved (results of the ocean retracking, accuracy in some geophysical parameters, …) • A bunch of SPRs accumulated on Level 2 DPMs/IODDs to be passed on to the IPF

5. Open items • e.g. new level 2 MWR algorithms (MWR water vapour content, wet tropo correction and cloud liquid water content for both RA2 and MWR MDS, and atmospheric attenuation corrections)

6. Level 2 algorithms verification subgroup • Objectives: • verification of all geophysical RA2 and MWR algorithms • algorithms used also in other missions (for these, only precision and impact on the output values will be checked) and new algorithms (for these, extensive verification will be needed) • which data used: FDGDR/FDMAR (IPF) and IGDR/IMAR, GDR and SGDR (F-PAC) • quantity of data used: small sets of data (2-3 orbits) to examine most of the output params, and then larger sets of data (7-35 days) t operform statistical analysis, fine tuning, ...

7. Level 2 algorithms verification subgroup • validation of the Level 2 products • verification of headers (consistency between the information in the headers and in the records) • verification of MDS parameters not verified before

8. Evolutions and updates mechanisms • Necessity of upgrade aux. files and algos near the end of CP may arise, following the work done by cal/val teams. • Requirement to upgrade aux. files/algos to be triggered by sub-group leaders (RA2 L1b, RA2 L2 and MWR): • ESLs to write SPR on applicable DPM, to validate it on a prototype processor (copy of the ref. processor) and to produce TDS (to test evolution on IPF/F-PAC) that will be delivered to the CCVT coordinator. • If deliverables acceptable, they’ll be passed to ESA/Alcatel interface for IPF and to ESA interface for F-PAC, for implementation • Time scale very short, since this evolution has to be done before the end of CP