1 / 86

CERES FM-5 NPP Science Processing Delta Design Review GSFC, MD August 26, 2008 Erika Geier

CERES FM-5 NPP Science Processing Delta Design Review GSFC, MD August 26, 2008 Erika Geier Jim Closs Denise Cooper Sunny Sun-Mack Lee Bodden Michael Little NASA Langley Research Center. Agenda. CERES Introduction Operations Concept Design Assumptions Science Data Processing

xenon
Download Presentation

CERES FM-5 NPP Science Processing Delta Design Review GSFC, MD August 26, 2008 Erika Geier

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. CERES FM-5 NPP Science Processing Delta Design Review GSFC, MD August 26, 2008 Erika Geier Jim Closs Denise Cooper Sunny Sun-Mack Lee Bodden Michael Little NASA Langley Research Center CERES FM-5 Delta Design Review

  2. Agenda CERES Introduction Operations Concept Design Assumptions Science Data Processing Requirements Instrument Subsystem Design Clouds Subsystem Design Testing Strategy ASDC Implementation Schedule Risk Analysis Issues/Concerns CERES FM-5 Delta Design Review

  3. CERES Mission Ground Systems • NASA Langley Research Center (LaRC) provides critical cloud and Earth radiation budget climate data records to support global climate change research • Past ERBE and current CERES instruments on TRMM (1), Aqua (2), and Terra (2), have provided 24 years of sustained radiation budget measurements • LaRC has collected over 30 Instrument years of CERES data from TRMM, Terra, and Aqua and has processed over 90% of that data to date CERES FM-5 Delta Design Review

  4. CERES Current Capabilities • Extensive LaRC CERES experience accumulated through the support of the five CERES instruments currently in orbit • Existing scientific expertise for the development, calibration, management and application of CERES data products • Data Center Operations already in place providing ingest, archival, production, management and distribution of CERES data products • Existing Science Computing Facility (SCF) for scientific analysis, investigations and development of CERES data products • Highly-experienced staff already in place supporting: • Ongoing algorithm investigation, development and enhancements • Implementation of algorithms into CERES Data Management System • Enhancements and development to current and new CERES data production systems • Production and distribution of CERES data products in a configured operations • The CERES DM task was successfully appraised at CMMI Capability Level 3 /Equivalent Maturity Level 2 CERES FM-5 Delta Design Review

  5. CERES Climate Analysis Research System (CARS) Organization Data Management Team (DMT) Atmospheric Sciences Data Center (ASDC) Science • Implements algorithms • Maintains software • Verifies data • Assists in validation • Provides CM and • documentation support • Ingests data • Places operational • software in production • Produces data sets • Distributes data sets • Archives data • Provides User Services • Derives & refines • algorithms • Validates algorithms • Validates CERES data • sets • Writes Quality Summary Algorithm Development Algorithm Implementation Data Production CERES FM-5 Delta Design Review

  6. Required CERES CARS Functionality • Provide Land PEATE sub-sampling software for aggregated VIIRS SDRs (Science and DMT) • Acknowledge data from SDS Land PEATE (ASDC) • Ingest data from SDS Land PEATE & other sources (ASDC) • Produce, archive, distribute data products (ASDC) • Report status of collection (ASDC) • Support user access to collection (ASDC) CERES FM-5 Delta Design Review

  7. CERES Operations Concept • CERES instrument raw data transmitted to the C3S and IDPS • IDPS creates CERES Raw Data Records (RDRs) and provides RDRs to the SDS SD3E and to ADS/CLASS • SD3E provides CERES RDRs and VIIRS xDRs to the Land PEATE • Land PEATE passes CERES RDRs along to ASDC • Land PEATE runs VIIRS Sub-sampler; provides output to ASDC • ASDC ingests and archives inputs coming from Land PEATE • ASDC generates and archives higher-level CERES products • ASDC distributes products to science researchers and public CERES FM-5 Delta Design Review

  8. NPOESS Systems CERES Operational Data Flow CERES Instrument Ops Team Commands, Loads and requests NPP Systems Mission Notices and Data NOAA Systems CERES Systems C3S CERES CARS Data and Science Operations Existing data, agreements Data Providers Mission Notices and Data requests SDS Data Distribution Data Users CERES RDRs, VIIRS Sub-samples & aerosols RDRs to PST Cmd & Tlm All RDRs SD3E L-PEATE RDRs SDRs EDRs IPs Svalbard IDPS Mission Data • Reuse existing systems and interfaces • System enhancements for NPP CERES All xDRs ADS CERES FM-5 Delta Design Review

  9. CERES Data Processing Design Assumptions • CERES CARS data processing development and operations leverages the existing personnel, procedures, production systems, and infrastructure already in place supporting CERES instruments on EOS Terra and EOS Aqua Missions • CERES CARS will use existing interfaces at the LaRC ASDC • CERES CARS software development is extensively reusing existing Terra/Aqua processing codes • Primary required NPP related enhancements are: • Use CERES raw data in new Raw Data Record (RDR) format: • Develop a preprocessor to distribute/sort RDR contents into Aqua-like files that can be used as inputs to existing CERES processing stream • Use VIIRS data products: • Use VIIRS sub-sampled calibrated radiance and aerosol products in place of instantaneous MODIS data. CERES FM-5 Delta Design Review

  10. NOAA IDPS Assumptions • Acquire CCSDS Packets • HDF Wrap CCSDS Packets • Generate & Stage RDRs for all APIDs for SDS & CLASS • Maintain CDFCB • Provide samples of each CERES RDR • Provide 28 hours of CERES RDRs for testing CERES codes at LaRC CERES FM-5 Delta Design Review

  11. SDS/Land PEATE Assumptions • Subscribe to SD3E for all CERES RDRs (Science, Diagnostic, and Housekeeping/Telemetry) • Acquire CERES RDRs and forward to ASDC via existing Land PEATE interface • Support CERES reordering of missing data • Produce aggregated VIIRS SDRs (MODIS HDF-EOS format) in 5 minute granules (VIAE, VMAE, VDAE). Sub-sample and ship 5 minute granules (VIMD) to ASDC • Produce VIIRS aerosol in 5 minute granules (VAOT) and ship to ASDC • Post-launch: When VIIRS calibration and/or algorithm changes, reprocess VIIRS from covers-open forward and ship to ASDC to support CDRs CERES FM-5 Delta Design Review

  12. Software Development Process Subsystem Product Integration and Verification Subsystem Updates and Unit Testing RequirementsManagement CM Validation and Product Integration ASDC Validation New Requirement Received, Logged, and Analyzed Updates Integrated Into Baseline Operational Testing at ASDC CM Testing Subsystem Science Testing Requirement Accepted and Assigned ValRx Testing Release to SIT Pre-CM Testing Software Development Process is in the following document currently under CERES Management review: Clouds and the Earth’s Radiant Energy System (CERES)National Polar-orbiting Operational Environmental Satellite System (NPOESS) Preparatory Project (NPP)Data Management System (DMS)Software Management Plan Version 0 Delivery to CM CERES FM-5 Delta Design Review

  13. Science Data Processing Approach for CERES FM-5 Processing is divided into 2 Streams: Instrument and ERBE-like Autonomous stream, dependent only on CERES data In production within 48 hours of power-on Aids in verifying Instrument health Critical for establishing CERES calibration/validation Produces ERBE-like data sets Data sets exist for CERES instruments on TRMM, Terra, and Aqua Similar data sets exist for ERBE instruments on ERBS, NOAA-9 and NOAA-10 Fused data sets beginning with Cloud/Convolution/Inversion processing and the SSF Use inputs from imager and other data sources Higher resolution imager data is Point Spread Function (PSF) weighted Produces higher quality climate data Data sets exist for CERES instruments on TRMM, Terra, and Aqua Will not be in production immediately after covers open Requirement is to ingest VIIRS radiance, geolocation, and aerosol data when it becomes available from Land PEATE CERES FM-5 Delta Design Review

  14. Simplified CERES Processing Flow Autonomous Subsystems affected by changing NPP inputs Autonomous CERES Subsystems CERES RDRs SSI Instrument SS2 Instantaneous ERBE-like SS3 ERBE-like TISA ES-4 BDS ES-8 ES-9 IES SS4 Compute Clouds, Convolve with CERES, compare TOA/surface fluxes VIIRS Radiances Geolocation Aerosols SS9 TISA Gridding SS10 TISA Averaging SSF SFC SRBAVG Subsystems affected by NPP input AVG SS5 Compute fluxes at levels SS6 TISA Gridding SS7 & 8 TISA Averaging CRS FSW ZAVG SYN CERES FM-5 Delta Design Review

  15. ERBE-like Averaging to Monthly TOA Fluxes 3 ERBE-like Inversion to Instantaneous TOA Fluxes 2 Geolocate and Calibrate Earth Radiances 1 INSTR: Instrument Production Data Set EID6: ERBE-like Regional Data BDS: BiDirectional Scans IES: InstrumentEarth Scans Determine CloudProperties, TOA and Surface Fluxes 4 ES-4: ERBE-like Monthly Geographical Averages ES-9: ERBE-like Monthly Regional Averages CRH: ClearReflectance History ES-8:ERBE-like InstantaneousTOA Estimates MODIS CID: VIIRS CID: CloudImager Data Compute Monthly &Regional TOAand Surface Averages 10 SFC: Monthly Gridded TOA/Surface Fluxes and Clouds SRBAVG: Monthly TOA/Surface Averages SSF: Single Scanner Footprint TOA/Surface Fluxes and Clouds GridTOA and SurfaceFluxes 9 MWH: MicrowaveHumidity Compute Surface &AtmosphericRadiativeFluxes 5 APD: AerosolData Regrid Humidityand TemperatureFields 12 MOA: Meteorological,Ozone, andAerosol Data GAP: Gridded Analysis Product CRS: Cloudsand Radiative Swath SURFMAP: SurfaceMap OPD: Ozone ProfileData Grid Radiative Fluxes and Clouds 6 Grid GEO NarrowbandRadiances 11 GEO: Geostationary NarrowbandRadiances GGEO: Gridded GEONarrowbandRadiances FSW: Monthly Gridded Radiative Fluxes andClouds SYN SynopticRadiative Fluxes & Clouds SYNI: Intermediate SynopticRadiative Fluxes and Clouds Compute Regional,Zonal andGlobalAverages 8 AVG: Monthly RegionalRadiative Fluxes& Clouds TimeInterpolate, ComputeFluxes 7 ZAVG: Monthly Zonal & Global Radiative Fluxes & Clouds Current CERES Climate Data Record Production Architecture CERES FM-5 Delta Design Review

  16. CERES Input Data Existing Data Source CERES FM-5 Delta Design Review

  17. CERES Publicly Available Output Products CERES FM-5 Delta Design Review

  18. Data Production Scenarios CERES strives to receive all possible FM-5 level 0 data and VIIRS data Instrument Ingest manager at ASDC to monitor missing RDR files and request those files from Land PEATE Land PEATE has agreed to provide CERES 99% of RDR files produced by IDPS within 1 month Data is actually processed three times Baseline1-QC run ~ 6 hours after end of the day. Used for quick instrument assessment. Files not needed after Edition1-CV processes. Edition1-CV run ~5-20 days after the end of the month. Assume all available data has been ingested. Calibration/Validation data set used to compute gains and spectral response functions. Edition2 run 6-12 months later using Edition1-CV as input. Applies best available instrument gains and spectral response functions. Cloud/Convolution/Inversion processing of the SSF Ingest manager at ASDC monitors missing MODIS files and requests missing files from MODAPS. VIIRS files to be handled in similar fashion. Once in routine production, Land PEATE has agreed to provide CERES 99% of available VIIRS files within 2 months of data date. Requires CERES and VIIRS radiance/geolocation data to avoid data gaps in SSF files If either one missing, a data gap results VIIRS aerosol data also needed. If unavailable, aerosol parameters set to CERES default fill values and no data gap results. Current Terra and Aqua SSFs typically run 6-12 months after data date. NPP processing will be very similar to Terra and Aqua. CERES FM-5 Delta Design Review

  19. CERES CARS Requirements Management CERES Level 3 and Level 4 requirements are being baselined in a CM-controlled document CERES Level 3 requirements have been reviewed by the SDS and will be provided to the SDS for inclusion in the SDS Requirements Specification Requirements change requires approval by Project Management and the Configuration Control Board Requirements are mapped into subsystem(s) for implementation Requirements are mapped into tests for verification and validation CERES FM-5 Delta Design Review

  20. CERES Data Sources CERES CARS Land PEATE CERES RDRs Instrument processing ERBE-like processing CERES RDRs VIIRS Geo/Rad SD3E VIIRS Geo/Rad Clouds processing Sub-sampling Archive, Distribution User Community VIIRS Aerosols VIIRS Aerosols VIIRS Subsample code 1- The Land PEATE receives CERES RDRs and VIIRS xDRs from the SD3E. 2- CERES RDRs are passed directly to the CERES CARS, where they are processed by the Instrument subsystem to produce inputs to the ERBE-like and Cloud subsystems. 3- The Land PEATE produces MODIS-like VIIRS radiance/geolocation and aerosol files. 4- The Land PEATE sub-samples the MODIS-like VIIRS radiance/geolocation data using software provided by CERES. 5- The Land PEATE sends the sub-sampled VIIRS files and the MODIS-like VIIRS aerosol files to the CERES CARS. 6- The CERES CARS runs the downstream subsystems, beginning with Clouds, as data becomes available. 7- Climate-quality data products are archived and made available to the user community along with Data Quality Summaries and user support. CERES FM-5 Delta Design Review

  21. CERES SDS Requirements NPP CERES FM-5 Science Data Segment Requirements: The ASDC Ingest subsystem shall have the capability of ingesting, verify by Checksum, and archiving CERES RDRs, sub-sampled VIIRS radiance/geolocation files, and VIIRS aerosol data received from the Land PEATE. The CERES CARS Preprocessor of the Instrument Subsystem shall have the capability of producing level-0, attitude, and ephemeris files as expected by the processing software. The CERES DMT shall have the capability of generating and delivering to the ASDC the following Science Subsystem code:- Instrument (at launch)- ERBE-like (at launch)- Clouds and subsequent subsystem software (12+ months after launch) The CERES DMT shall provide software to the Land PEATE to sub-sample VIIRS radiance/geolocation files, and work with the Land PEATE to ensure that the sub-sampling code executes properly. CERES FM-5 Delta Design Review

  22. CERES SDS Requirements NPP CERES FM-5 Science Data Segment Requirements (cont.): The CERES DMT shall have the capability of modifying and redelivering production code for all 12 CERES Subsystems to produce CERES NPP data products. The ASDC shall have the capability of generating, archiving, and disseminating climate-quality data products. The CERES DMT and Science Team shall have the capability of validating and writing quality summaries for all CERES data products. The ASDC shall have the capability of providing quality summaries and user support for data customers. CERES FM-5 Delta Design Review

  23. Requirements Verification • Baseline LaRC FM-5 L4 requirements by placing CERES CARS Requirements Specification Document on NX (CERES CARS, 09/2008) • Baseline SDS FM-5 L3 requirements by adding CERES to SDS Requirements Specification Document (SDS, 09/2008) • Map FM-5 L3 requirements to SDS Testing Scorecard and schedule (Vic Buczkowski, 10/2008) • Produce Requirements Traceability Matrix to map LaRC L4 requirements to CERES CARS Subsystems and test cases (CERES CARS, 10/2008) • Conduct FM-5 SDS L3 testing as documented in SDS Testing Scorecard (SDS/LaRC Test Team, (02/2009) • Conduct FM-5 LaRC L4 testing as documented in LaRC Requirements Traceability Matrix (LaRC Test Team, (mid-2009) CERES FM-5 Delta Design Review

  24. Instrument Subsystem Design Approach Instrument Design Approach and CERES DMT RDR Tests Denise Cooper Contributing Team Members: Ashley Alford Dale Walikainen Mark Timcoe CERES FM-5 Delta Design Review

  25. Instrument Design Approach • Extensive reuse of existing software for instrument subsystem • Proven system used for current CERES processing • Majority of software written in Ada • Newly developed code to be in C++ • RDR Preprocessor • Creates 24-hr Level-0 and Toolkit compliant Ephemeris and Attitude data files • Ada code will be updated to allow processing of FM-5 data • PGE to process incoming NPP Level-0 data will be the first priority, other PGEs will be converted following successful testing of this PGE. CERES FM-5 Delta Design Review

  26. Instrument Design Approach • PGE providing data to ERBE-like already in C, only changes will be to allow processing of FM-5 data. • Initial version of all code will use the SDP Toolkit due to schedule constraints. Updates to remove dependency on the SDP Toolkit expected after launch. • CERESlib updates to create a C-version of existing F90 Metadata creation routines. • Facilitate integration of existing Metadata with Ada, C and C++ software. CERES FM-5 Delta Design Review

  27. NPP Instrument Subsystem Coeff Data CERES RDRs 2 files needed to process (time span noon yesterday - noon today) To ERBE-Like Ephemeris Data ~133 Science & Diagnostic RDRs with Diary data BDSs Pre-ES8 Up to 6 files per day BDS, BDSS, BDSD, BDSM, BDSP & BDSG (HDF4 SDS & Vdatas containing Geolocation values Raw data counts Filtered radiances Instrument H&S info) 1 file per day (Binary containing Geolocated, Filtered radiances) L0 Data Preprocessor Geolocate & Calibrate Pre-Es8 Generator Up to 3 files per day (Science, Calibration & Diagnostic) Attitude Data IESs Attitude Data Attitude Data Attitude Data Attitude Data Up to 24 files per day (HDF4 Vdata containing Geolocation values Filtered radiances) To Convolution 14 files needed to process (time span hr 22 day before - hr 00 next day) CERES FM-5 Delta Design Review

  28. ERBE-like Spectral Corrections Spectral Response Function No code changes needed to support NPP Unfiltering Coefficients Unfiltering Modtran Data CERES FM-5 Delta Design Review

  29. ERBE-like Inversion Unfiltering Coefficients No code changes needed to support NPP From Instrument Subsystem ES4 EID6 Pres8 1 file per month (HDF4 containing Regional, Zonal & Global Gridded fluxes) 1 file per day (Binary database Info) 1 file per day (Binary containing Geolocated, Filtered radiances) Monthly Averaging Daily Inversion ES9 ES8 1 file per month (HDF4 containing Global Average fluxes) 1 file per day (HDF-EOS4 containing Geolocated Filtered & Unfiltered radiances & fluxes) CERES FM-5 Delta Design Review

  30. CERES DMT RDR Tests • Objectives • Ensure the RDR preprocessor is able to read the CERES Science and Diagnostic RDR HDF5 files and create the properly formatted Level-0, Ephemeris and Attitude data files that are compatible with the updated Ada and the converted C++ code. • Description • Assume ingest of RDRs by ASDC; Alternative is to access RDRs stored in specified location if not available from the ASDC • Test with selected RDRs on the development platform to provide output that will be used by the Level-0 data processor to show that output Level-0, Ephemeris and Attitude data is as expected by this PGE. • Test on the development platform with minimum of 28-hrs of RDR data through the Level-0 PGE, on to the Pre-ES8 generator to create the data used by ERBE-like. CERES FM-5 Delta Design Review

  31. CERES DMT RDR Tests • Description (Cont’d) • Pre-delivery testing on production platform to ensure all systems work on the production platform and generate scientifically equivalent data. • Ensures all software works as expected on the production platform before delivery • Provides expected output used by CM to verify their test results • CM testing using Instrument Subsystem Test Plan to verify that all necessary updates have been delivered and provide output equivalent to the provided expected output. • ASDC SIT operational testing: e.g. Dec. 31, Jan. 1, Feb. 28/29, etc. • Participants • Ashley Alford, Denise Cooper, Mark Timcoe, Land PEATE, LaRC ASDC SIT CERES FM-5 Delta Design Review

  32. CERES DMT RDR Tests Science Level-0 File RDRs Science & Diagnostic ~133 per data day (Level-0 packets & Diary data) Calibration Level-0 File RDR Pre-processor Diagnostic Level-0 File Total 10391 packets Per data day Ephemeris Data Files Attitude Data Files Data files (Noon previous day - Noon next day) 12 Data files (2 hr data per file) CERES FM-5 Delta Design Review

  33. Instrument Schedule • RDR Format Documentation Provided (Jun. 2008) • Unpacking of RDR Wrapper Implemented (Jul. 2008) • Conversion of RDR Contents to CERES Level 0 Format Implemented (Sep. 2008) • Selection and Conversion of Attitude/Ephemeris Data Implemented (Sep. 2008) • Informal Testing with Actual RDR (dependent on IDPS providing early RDR) (Oct. 2008) • Instrument Subsystem Enhancements Integrated and Tested (Dec. 2008) • Instrument Subsystem Verification Testing Complete (Jan. 2009) • Delivery to ASDC through DMT CM for Formal Validation Tests (by Mar. 13, 2009) CERES FM-5 Delta Design Review

  34. Clouds Subsystem Design Approach CERES Clouds Subsystem Design Approach and CERES DMT VIIRS Tests Sunny Sun-Mack Contributing Team Members: Yan Chen Walt Miller CERES FM-5 Delta Design Review

  35. CERES SSF Processing(Subsystem 4) Subsystem 4 - Determine CloudProperties, TOA and Surface Fluxes, is made up of 3 different sets of code Clouds - VIIRS inputs will necessitate changes to support NPP Processes the imager data Resulting pixel-level output written to temporary file Convolution - minor changes needed to support NPP Merges the pixel-level data with the CERES footprint data Resulting footprint-level output written to a temporary file Inversion - no change needed to support NPP Reads the footprint level output file containing CERES radiance data and cloud properties Computes unfiltered radiances, TOA fluxes, and surface fluxes Generates the SSF data product which is archived and publicly released CERES FM-5 Delta Design Review

  36. NPP Impact on CERES Clouds and Convolution Design Approach VIIRS will replace MODIS as imager source Ability to generate certain cloud properties changes Some radiances, CO2 slicing, may be missing CERES IES (input from Instrument Subsystem) interface will remain the same New Point Spread Function (PSF) ancillary file will be generated to account for VIIRS imager resolution SSF interface change possible as CERES migrates to Edition3 CERES FM-5 Delta Design Review

  37. Clouds Subsystem Design Approach • Newly developed VIIRS sub-sampling code at LaRC • VIIRS Sub-sampling Preprocessor • Written in C language • Input: NPP_VIAE ( Radiances from Imaging “I” Channels ) NPP_VMAE ( Radiances and geolocations from Moderate-Resolution “M” Channels) NPP_VDNE ( Radiances and geolocations from Imaging Day-Night Band (channel) “DNB” ) • Output: NPP_VIMD_SS ( Radiances and geolocations from all above three Imaging, Moderate and DNB, but sub-sampled and sub-channeled with certain channels being averaged ) CERES FM-5 Delta Design Review

  38. Clouds Subsystem Design Approach • VIIRS sub-sampling code will run at the Land PEATE • The package to be delivered to Land PEATE by CERES CM at LaRC • VIIRS sub-sampling code • Process Control Generator to produce process control file (PCF) • Input data and Expected sub-sampled output • Test Plan (PDF) • VIIRS sub-setting code will be run at Land PEATE • The output from VIIRS sub-sampling code, NPP_VIMD_SS, will be produced at Goddard Land PEATE • Land PEATE will then deliver NPP_VIMD_SS to LaRC ASDC • LaRC ASDC will ingest and archive NPP_VIMD_SS • NPP_VIMD_SS will be the Cloud Imagery Data (CID) as input to CERES Clouds Subsystem. CERES FM-5 Delta Design Review

  39. NPP_VIAE NPP_VIMD_SS I1 = 0.64 m I2 = 0.865 m I3 = 1.61 m I4 = 3.74 m I1 = 11.45 m I1 = 0.64 m I3 = 1.61 m I4 = 3.74 m I1 = 11.45 m VIIRS Sub-setting Data Formats • Sub-setting NPP_VIAE Resolution: 375 meter Radiances from VIIRS Imaging Channels Sub-setting Channels CERES FM-5 Delta Design Review

  40. VIIRS Sub-setting Data Formats • Sub-setting NPP_VIAE ( Cont’d) Averaging 4 Imaging Pixels to 1 Moderate Resolution Pixel I Pixels (NPP_VIAE) M Pixels (NPP_VIMD_SS) CERES FM-5 Delta Design Review

  41. VIIRS Sub-setting Data Formats • Sub-setting NPP_VIAE ( Cont’d) Sub-setting Samples NPP_VIAE Scan-lines x Pixels = 4608 x 6400 Every other pair of scan-lines Every other pair of pixels NPP_VIMD_SS Scan-lines x Pixels = 2304 x 3200 CERES FM-5 Delta Design Review

  42. VIIRS Sub-setting Data Formats 1. Sub-setting NPP_VIAE ( Cont’d): SDSs Kept CERES FM-5 Delta Design Review

  43. VIIRS Sub-setting Data Formats Sub-setting NPP_VIAE ( Cont’d): The SDSs not being subset CERES FM-5 Delta Design Review

  44. VIIRS Sub-setting Data Formats 2. Sub-setting NPP_VMAE Resolution: 750 meter Radiances and Geolocation from VIIRS Moderate Channels Sub-setting Channels CERES FM-5 Delta Design Review

  45. VIIRS Sub-setting Data Formats • Sub-setting NPP_VMAE ( Cont’d) Sub-setting Samples NPP_VMAE Scan-lines x Pixels = 3072 x 3200 Every other scan-line Every other pixel NPP_VIMD_SS Scan-lines x Pixels = 1536 x 1600 CERES FM-5 Delta Design Review

  46. VIIRS Sub-setting Data Formats 2. Sub-setting NPP_VMAE (Cont’d) NPP_VMAE and NPP_VIMD_SS All Geolocation Info in NPP_VMAE is included in the Subset NPP_VIMD_SS NPP_VMAE: Global Attributes NPP_VIMD_SS: SDS (64 bits float) CERES FM-5 Delta Design Review

  47. VIIRS Sub-setting Data Formats • 2. Sub-setting NPP_VMAE (Cont’d): SDSs Kept CERES FM-5 Delta Design Review

  48. VIIRS Sub-setting Data Formats 2. Sub-setting NPP_VMAE (Cont’d): SDSs Kept CERES FM-5 Delta Design Review

  49. VIIRS Sub-setting Data Formats 2. Sub-setting NPP_VMAE ( Cont’d): The SDSs not being subset CERES FM-5 Delta Design Review

  50. VIIRS Sub-setting Data Formats 2. Sub-setting NPP_VMAE ( Cont’d): The SDSs not being subset CERES FM-5 Delta Design Review

More Related