1 / 5

F-PAC validation context

F-PAC validation context. CMA chain has to be inline with the algorithms approved by ESA and used for the prototype development CLS Prototype validated : using Test Data Sets based on ERS-2 and T/P data with real Envisat data : header part all fields in the data set records

kareem
Download Presentation

F-PAC validation context

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. F-PAC validation context • CMA chain has to be inline with the algorithms approved by ESA and used for the prototype development • CLS Prototype validated : • using Test Data Sets based on ERS-2 and T/P data • with real Envisat data : • header part • all fields in the data set records • CalVal analysis • --> Validation OK • CMA validated with respect to the prototype outputs • some known anomalies • some known discrepancies agreed with ESA • --> Validation OK, further validation handled by the CalVal team RA2 CCVT meeting - 25-27 March 2003

  2. F-Pac known “issues” • None on the POE processing • Request for waivers on the CMA chain : • No Bent correction (agreed with ESA) • specific DEM used for bathymetry/elevation determination (agreed with ESA) • default strategy for ice1&sea-ice parameters • Issues : • position in the header part but the Product Spec state: • The Orbit State Vector (OSV) corresponds to the Ascending Node crossing if the OSV is generated from the DORIS Navigator Level 0 product (DOR_NAV_OP), or from the FOS Predicted Orbit (AUX_FPO_AX). The OSV corresponds to sensing start time of the product if the OSV is generated from the DORIS preliminary product (DOR_POR_2P), DORIS precision product (DOR_VOR_2P), or from the FOS Restituted Orbit (AUX_FRO_AX). • duplicated products RA2 CCVT meeting - 25-27 March 2003

  3. F-Pac known “issues” • Current anomalies on the CMA chain : • some level2 records filled with Nan values • wrong method used for the atmospheric attenuation (used of the sigma0_S value instead of the Ku one) • --> impacts the sigma0 and so the wind and the SSB (so the SLA) • radiometer interpolation method different from the reference prototype • --> impacts the radiometer parameter close to land • MCD fields / prototype values in particular for the ice1 and sea-ice values • Doris ionospheric chain has to be tuned • Pass number used instead of the Orbit Number in the header part • tide management (long period term) RA2 CCVT meeting - 25-27 March 2003

  4. “Known limitation” • On the Aux data files : • SSB table used is the ERS2 Ku band table on both Ku and S band --> impacts the dual frequency ionospheric correction • rain flag : • table estimated for the S band • and cloud liquid water content biased • GSFC00.1 MSS used (limited in latitude bandwidth) RA2 CCVT meeting - 25-27 March 2003

  5. Data validation • IGDR daily validation by Xover and statistic analysis • GDR cycle basis validation • ocean retracking • ice retrackings • Multi-mission data quality (Envisat/ERS-2/Jason-1) • Long term validation • annual report for the above tasks Cycle 11 validation report RA2 CCVT meeting - 25-27 March 2003

More Related