1 / 6

Ocean Salinity Processor Project Status Update

An update on the Ocean Salinity Processor Project as of September 17, 2008, detailing its progress, developments, and future plans. Includes information on transition activities, AlgoVal meetings, processor enhancements, quality information, and more.

osias
Download Presentation

Ocean Salinity Processor Project Status Update

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. Level 2 Ocean Salinity ProcessorProject Status 17 September 2008 Samantha Lavender Paul Spurgeon Caesar Mugerin

  2. Project status • April 2008 start • Contract signed July 2008 • Target platform acquired September 2008 • ACRI-st to ARGANS transition activities: • May: science & software: documentation (ATBD, DPM...), processor architecture design & implementation, schema, L2 prototype GUI... • July: AlgoVal • September: End-To-End

  3. Project status • AlgoVal meetings #10 (May) & 11 (July) & 12 • SMOS L2 OS web site transferred & updated • http://www.enviport.org:8080/argans/ • smos, sss2008 • includes builds, actions, change requests, & documentation databases • AlgoVal Plan & End-To-End analysis

  4. Towards V4 • Operational Processor clean build for V3+ • Code & DPM review, bug fixes (full pol, convergence algorithm, Stokes vector error) • new prototype processor for ESLs • Updated documentation & SVVP

  5. Proposed format changes • SPH quality information • classify grid points by geophysical characteristics • for each class, collect a set of values describing retrieval quality: • number flagged as poor quality, failing for specific reasons, successes, average sigma • AGDP bias/sigma & priors LUT re-specification • Tb/sigma model specification? • Tb full covariance matrix specification?

  6. AlgoVal & End-To-End status

More Related