Introduction More delays for Flavio. Visa appointment in Mexico for Jan 9 th Likely start date: Second half of Jan. MIRS 3 rd Release delivered on December 15 th as scheduled The following slides present the main features of this release and the latest developments since pre-release

What to expect in this 3 rd release New algorithms implemented for the surface properties (SWE, SIC, Snow Cover) based on emissivity New parameters delivered for testing purposes (Snow effective grain size, Multi-Year, First-Year Sea ice concentrations, Surface Type) Improved Science (Footprint matching, Bias correction, Preclassification, First-Guess from Regression, NEDT computation) Higher convergence rates over all surfaces System/Format changes to account for OSDPD feedback System/Format changes to accommodate new products

Science Updates Non-Convergence Non-convergence was handled by a number of things: -Use of first guess -Implementation of range checking -measures for emissivity

Science Updates Footprint Matching Automatic synchronization Manual synchronization Synchronization (or geolocation) issues between AMSU and MHS We reverted back to manual synchronization Drawback: we might see again missing scanlines

Science Updates New Algorithms for Surface Properties Based on MIRS emissivities Use physical model Comparison to MSPPS and to IMS See Cezar’s presentation

Science Updates(5/8) New Products (not officially delivered) Case of Sea Ice Concentration First-Year SIC Multi-Year SIC Total Sea Ice

Science Updates(6/8) New Products (not officially delivered) Case of Snow Snow Water Equivalent Snow Effective Grain Size Snow Cover (by product)

DescriptionCommentsStatus 1 Non zero exit code should be issued for any abnormal exit. [Interpretation: All BASH scripts exits should have error codes returned.] Most of exits had returned codes. A few did not have any. This was fixed. OK 2 Error code check need be added for script functions at each step [Interpretation: Test the status returned after each step (script)] Script functions have been tested but internally. Added tests in scripts to check status of execution in each step. OK 3 Op_msg should only be used for fatal errors This was the case for all F90 codes. Pb was with script functions. All script functions do now use op_msg only for fatal errors and echo for the rest. OK 4 Other error messages for monitoring or diagnostics purpose should be re-directed to another log file (non- zero but not 99). [Same as item3] Needs clarification (assumed to be same as item 3) OK Handling Feedback from OSDPD (1/3)

DescriptionCommentsStatus 5 Set-up “lock” to allow only one orbital processing per satellite to avoid duplicated jobs or competition for resources. This is implemented in OSDPD using wrapper. The same wrapper could be used for newer versions of MIRS. OK 6 A non-zero return code should be issued when no footprint match data found or the number of the retrieved Profiles is zero When no valid FM profiles found, process returns code to script. OK 7 QC check for radiance using scanline quality flag provided in 1b Needs clarification. Not sure we understand the meaning of this remark. Assumed related to the zero-valid scanlines issue. Problem fixed at the RDR2TDR level. OK Note: Let us know if meant something else. 8 Can scanline information be saved? – lack of this information would put drawback on data provided and limits/impacts for users to use exist visualization tools Scanline # added from footprint matching to EDR and DEP files. Note that there might be gaps if scanline is missing or mis- synchronization found. OK Handling Feedback from OSDPD (2/3)

DescriptionCommentsStatus 9 Directory structures, file name conversion should be Simple, unique and consistent crossing sensors and satellites. The MIRS package controls all directory structure through setup file (PCF), making it possible to use any directory structure wished by user. We have streamlined many directories (see next item). If needed, directory structure could be further changed through PCF (Paths and Configuration File). OK 10 Unique Sat_ID and sensor_ID are recommended to be added in the name conversion for sensor or satellite dependent subroutine, static files, scripts, load modules and makefile Convention used previously (satId_sensorId) for sensor- specific scripts, executables, Inputs and Control Files. Now extended to all Static (Cov, CRTM, Nedt, Antennas, etc), Semi-Static data (Regression, Bias) and src/ files as well when sensor specific items are needed. OK Note: For makefiles, we use standard procedure in software industry (tree-type generic makefiles for all applications. No sensor names in makefiles) 11 Using color code or turn the track tool on to allow the changes be clearly tracked for each version. -OK 12 Make sure are the content of docs are consistent with the codes and data delivered. -OK 13 A set of Word Docs with the changes identified should be delivered to OSDPD if the.pdf files are preferred in the DAP for public. -OK Handling Feedback from OSDPD (3/3)

Work Accomplished Since pre- release (Dec 15 th 2007) Further validation of the surface properties (SWE, SIC) [See Cezar’s presentation] Documentation Updates Finalization of the update to the first guess Finalization of the validation of the sounding Finalization of the new features of the system monitoring tool (scientific monitoring comprised of comparisons to GDAS and MSPPS)

MIRS Web site Central piece of the (1) MIRS quality monitoring but also of (2) the scientific validation of all products and (3) scientific improvement See Web site demo –Number of iterations added –SWE, SIC (and derived products) added –More sounding layers added for monitoring –Sounding validation wrt GDAS