170 likes | 324 Views
Using ADL for NPP Climate Raw Data Record Production. James C. Biard Cooperative Institute for Climate and Satellites – NC (CICS-NC)* North Carolina State University, Asheville, NC USA, and NOAA’s National Climatic Data Center (NCDC ) Climate Data Record Program Asheville, NC USA.
E N D
Using ADL for NPP Climate Raw Data Record Production James C. Biard Cooperative Institute for Climate and Satellites – NC (CICS-NC)* North Carolina State University, Asheville, NC USA, and NOAA’s National Climatic Data Center (NCDC) Climate Data Record Program Asheville, NC USA
What is a Climate Raw Data Record? A C-RDR is an intermediate step between a Raw Data Record and a Sensor Data Record. Raw measurements collected into time series variables, accompanied by the coefficients and tables needed to convert them to science units and calibrate them. (NOAA Level 1b) Needed for climatescience processing done many years from now.
C-RDR Features • Standards-based Platform Independence • netCDF-4 • Measurements, Processing Coefficients, and LUTs stored as variables (no C structs). • Robust Metadata • Each variable annotated with information extracted from the CDFCB-X and MDFCB. • Climate and Forecast Conventions • Attribute Convention for Dataset Discovery • Includes relevant NPP file-level metadata
C-RDR Data Products • C-RDRs planned for ATMS, CrIS, OMPS, and VIIRS. • One C-RDR contains two types of files: • Data files (contain raw data from RDRs) • Support Data (SD) files (contain PCs and LUTS) • VIIRS C-RDR to go into production in January 2013.
ADL: The perfect C-RDR application framework Provides all the code needed to access the raw measurements, PCs, and LUTs Able to decompress images, perform geolocation, etc Object-oriented design allows for customization without modification of framework source code Was able to build a C-RDR framework layer
C-RDR Framework • Two types of applications needed for each product (ATMS, CrIS, OMPS, & VIIRS) • C-RDR Packer (RDRs to C-RDRs) • Support Data Packer (AUX files to C-RDR SDs) • Two types of applications needed for verification testing • C-RDR Unpacker (C-RDRs to SDRs) • Support Data Unpacker (C-RDR SDs to AUX files)
C-RDR Packer Requirements Do per-job initializations common to all C-RDR packer algorithms (reading C-RDR-specific config parameters, creating output netCDF file, …). Do common per-granule initializations. Do common per-job finalizations (writing file-level metadata, closing output netCDF file, …).
C-RDR Support Data Unpacker Requirements Create “binary blob” AUX files from the input C-RDR SD file. Populate “.asc” metadata files for the AUX files with values from the input C-RDR SD file.
C-RDR Unpacker Requirements Populate task list from science data granules in the input C-RDR file. Populate the input map with spacecraft diary granules from the input C-RDR file. Put appropriate metadata on all input and output data objects so that processing can continue as if the data came from original “binary blob” RDR files.
Conclusions The ADL framework is complex, but provides ample room for customization. Finding the right method to override can be tricky. ADL saved the C-RDR project a tremendous amount of time.
For more information: Jim Biard – jim.biard@noaa.gov Drew Saunders – drew.saunders@noaa.gov Linda Copley – linda.copley@noaa.gov This work was supported by NOAA through the Cooperative Institute for Climate and Satellites - North Carolina under Cooperative Agreement NA09NES4400006 This work is a project of the NOAA NCDC Climate Data Record Program