Thursday, 24 January 2008: 9:15 AM
NOAA/NESDIS GOES-R Algorithm Working Group (AWG) and its Role in the Development and Readiness of GOES-R Product Algorithms
R02-R03 (Ernest N. Morial Convention Center)
For the next-generation of GOES-R instruments to meet stated performance requirements, state-of-the-art algorithms will be needed to convert raw instrument data to calibrated radiances and derived geophysical parameters (atmosphere, land, ocean, and space weather). The GOES-R Program Office (GPO) assigned the NOAA/NESDIS Center for Satellite Research and Applications (STAR) the responsibility for technical leadership and management of GOES-R algorithm development and calibration/validation. STAR responded with the creation of the GOES-R Algorithm Working Group (AWG) to manage and coordinate development and calibration/validation activities for GOES-R proxy data and geophysical product algorithms. The AWG consists of 15 application teams that bring expertise in product algorithms that span atmospheric, land, oceanic, and space weather disciplines. Each AWG team will leverage science developments from the GOES-R Risk Reduction Program, potential scientific algorithms from other communities (other government agencies, universities and industry), and heritage approaches from current operational GOES and POES product systems. All algorithms will be demonstrated and validated in a scalable operational demonstration environment. All software developed by the AWG will adhere to new standards established within NOAA/NESDIS. The AWG Algorithm Integration Team (AIT) has the responsibility for establishing the system framework, integrating the product software from each team into this framework, enforcing the established software development standards, and preparing system deliveries to the GOES-R Ground System contractor. The AWG will deliver an Algorithm Theoretical Basis Document (ATBD) for each GOES-R geophysical product as well as Delivered Algorithm Packages (DAPs) to the GPO. The DAPs will include pre-operational algorithm source code, related software development files such as program scripts, make files, and process control files; software and installation documentation, software tool kits required for compilation (NetCDF, HDF, etc); proxy (simulated input/output) test data sets; coefficient files; and test programs/test information including test descriptions, plans & procedures, and performance testing results.
Supplementary URL: