Microwave Integrated Retrieval System
This presentation is the property of its rightful owner.
Sponsored Links
1 / 135

Microwave Integrated Retrieval System for NPOESS Preparatory Project: MiRS NPP/ATMS Integration into NDE Code Unit Test Review May 26, 2011 PowerPoint PPT Presentation


  • 80 Views
  • Uploaded on
  • Presentation posted in: General

Microwave Integrated Retrieval System for NPOESS Preparatory Project: MiRS NPP/ATMS Integration into NDE Code Unit Test Review May 26, 2011. Prepared By: Kevin Garrett 1 Chris Grassotti 1 Sid-Ahmed Boukabara 2 Flavio Iturbide-Sanchez 1 Wanchun Chen 3

Download Presentation

Microwave Integrated Retrieval System for NPOESS Preparatory Project: MiRS NPP/ATMS Integration into NDE Code Unit Test Review May 26, 2011

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Microwave Integrated Retrieval Systemfor NPOESS Preparatory Project:MiRS NPP/ATMS Integration into NDECode Unit Test ReviewMay 26, 2011

Prepared By: Kevin Garrett1

Chris Grassotti1

Sid-Ahmed Boukabara2

Flavio Iturbide-Sanchez1

Wanchun Chen3

Leslie Moy1

1 I.M. Systems Group

2 NOAA/NESDIS/STAR

3 Dell


Review agenda

Review Agenda

1. Introduction 1:30 – 1:40K. Garrett

2. TRR Report 1:40 – 2:00C. Grassotti

3. Unit Test Plan 2:00 – 2:10C. Grassotti

4. Code Unit Tests2:10 – 3:20

Context and System LayerC. Grassotti

MiRS DAP Unit TestsC. Grassotti

QC DAP Unit TestsK. Garrett

5. System Test Plan3:20 – 3:25K. Garrett

6. Risks/Actions 3:25 – 3:35K. Garrett

7. Summary and Conclusions3:35 – 3:40K. Garrett

Discussion 3:40 – 4:00All


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • INTRODUCTION

  • TRR Report

  • Unit Test Plan

  • Code Unit Tests

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • Risks/Actions

  • Summary and Conclusions

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 1 –

Introduction

Presented by

K. Garrett


Project objectives

Project Objectives

  • Technical Objective

    • Adaptation of MiRS to NPP ATMS and integration within NDE

  • Science Objectives

    • Improved temperature and moisture profile retrievals

    • The extension of the retrieved products to non-standard surfaces including sea-ice and snow-covered land

    • The retrieval in all-weather conditions including cloudy and precipitating conditions

    • An improved set of retrieved surface properties whose derivation is based on the retrieved emissivities instead of directly from the brightness temperatures


Cutr objectives

CUTR Objectives

  • Objectives of the Code Unit Test Review

    • Goal #1: Gather all MiRS stakeholders to review the overall system integration of MiRS into the NPOESS Data Exploitation (NDE) environment

    • Goal #2: Review of MiRS Software Code Unit Tests

    • Goal #3: Review of MiRS System Test Plan

    • Goal #4: Review of TRR action items and actions taken

    • Goal #5: Identify new or outstanding risks w/mitigation strategies

  • Follow the STAR EPL Guidelines for CUTR


Mirs stakeholders

MiRS Stakeholders

  • Development Team

    • S.-A. Boukabara, K. Garrett, F. Iturbide-Sanchez, C. Grassotti, W. Chen, L. Moy

  • OSPO Partners

    • L. Zhao, J. Zhao, T. Conrad

  • NDE Partners

    • P. MacHarrie, L. Fenichel, D. Powell, J. Silva, G. Goodrum

  • MiRS Oversight Board

    • F. Weng (chair), R. Ferraro (STAR), L. Zhao (OSPO), J. Silva (NDE), T. Schott (OSD)

  • Oversight Panels

    • SPOP, PREPOP, ICAPOP, LSPOP

  • MiRS Users

    • Dan Pisut (NOAA EVL), Tony Reale (STAR), Joe Turk (JPL), Ben Ruston (NRL), Sheldon Kusselson (SAB), Stan Kidder (CIRA), Kevin Schrab and Andy Adman (NWS), Denise Hobson (AFWA), M. Kim (JCSDA), G. Huffman and W. McCarty (NASA/GSFC), J. Tesmar (FNMOC), P. Wang (Taiwan Weather Bureau), J. Janowiak (UMD), Paul Field (UKMET), K. Okamoto (JMA), M. V. Engel (IAO SB), B. Lambrigtsen (JPL), Peiming Dong, Qui Hong and Hu Yang (CMA), Universities (Graduate School of Chinese Academy of Sciences, Universiadeglistudidi Roma), Franklin Robertson and Clay Blankenship (NASA/MSFC), Tom Auligne (NCAR), D. Vila (CPTEC, Brazil), W. Han (Chinese Met. Admin.), D. Cimini (IMAA/CNR), M. Itkin (MPI-M, Hamburg), T. Greenwald (SSEC), + several new users since TRR (Jan 2011)


Mirs in nde timeline

MiRS in NDE Timeline

Sep’09

PDR for NPP ATMS

Jan’10

QC for NPP Review

Jan’11

TRR for NPP ATMS

Jun’10

CDR for NPP ATMS

Mar’09

Initial version

of MiRS Integrated

at NDE

L+90

Official DAP delivery to NDE

Jun’09

Development

with proxy data begins

Oct’11

NPP scheduled for launch (was Jan’11)

Jul’09

Jan’10

Jul’10

Jan’11

Jan’09

Oct’11

Oct’11-L+90

Post launch activities

Calibration

Validation

FG/bias/preclassifier

SRR (Jan ‘12)

etc

Nov’09-Dec’10

Enhanced MiRS

development (advanced footprint matching, proxy data SDRs, QC DAP)

Aug’09

Updated version of MiRS implemented at NDE and STAR

(full ATMS functionality)

Feb’09

Integration into NDE work begins

May ‘11

CUTR for NPP ATMS

Oct’09

Process multiple sample data granules from IDPS

Dec’10

QC DAP Initial Delivery

May’09

Official version of MiRS integrated


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR REPORT

  • Unit Test Plan

  • Code Unit Tests

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • Risks/Actions

  • Summary and Conclusions

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 2 –

TRR Report

Presented by

C. Grassotti

  • Review of TRR Action Items

  • CUTR Entry Criteria

  • CUTR Exit Criteria

  • TRR Summary


Trr action items

TRR Action Items

  • Total of 5 Action Items

    • For each AI, response was drafted (when available) describing the item, the action(s) (to be) taken, and status

    • Response sent to AI author(s)

    • At present:

    • 4 Items Closed

    • 1 Item Remains Open


Trr action items1

TRR Action Items


Action item 1 include test procedures in code unit test review

Action Item # 1: Include Test Procedures in Code Unit Test Review

Submitted by: G. Goodrum

Description:STAR to include test sequences and procedures at Code Unit Test Review. This will encapsulate testing of MiRS individual code units and verification of corresponding input/output.

Lead Organization:STAR

Response: These actions to be implemented in this CUTR

Status:OPEN (expected closed after CUTR)


Action item 2 request footprint matching code from ipo

Action Item # 2: Request Footprint Matching Code From IPO

Submitted by: STAR

Description:Pursue footprint matching codes for NPP/ATMS from IPO through T. Schott. This is FM code to optimize spatial resolution and sampling characteristics of ATMS SDRs, taking advantage of the ATMS sensor oversampling at many frequencies. This addresses Risk #3 from the MiRS CDR.

Lead Organization:STAR/OSD

Response:T. Schott submitted formal request for FM code. Code has been received. Code is in MatLab (no documentation provided), and only computes the Backus-Gilbert weighting coefficients. Following up with MIT to inquire about code that applies the coefficients/FM code.

Status:CLOSED


Action item 3 meet with ospo to discuss mirs tier 3 qc feasibility

Action Item # 3: Meet with OSPO to Discuss MiRS Tier-3 QC Feasibility

Submitted by: L. Zhao

Description:MiRS IPT to meet with OSPO (L. Zhao) to discuss MiRS Tier-3 QC feasibility, resource requirements, etc. This relates to CDR AI #7 which requires OSPO to draft RFA for implementing Tier-3 QC into operations, if deemed feasible.

Lead Organization:STAR/OSPO

Response:MiRS IPT met with OSPO on 16 Feb 2011 to discuss Tier-3 feasibility. (Tier-3, Geophysical monitoring)

Status:CLOSED


Action item 4 meet with nde to discuss mirs qc dap implementation

Action Item # 4: Meet with NDE to Discuss MiRS QC DAP Implementation

Submitted by: D. Powell

Description:MiRS IPT to meet with NDE (D. Powell) to discuss MiRS QC DAP implementation and integration plan, and capabilities. Outcome to determine the utility of the various monitoring tools of the QC DAP.

Lead Organization:STAR/NDE

Response:MiRS IPT (K. Garrett) met with NDE to outline capabilities and requirements of QC DAP within NDE system

Status:CLOSED


Action item 5 assessment of mspps algorithms with atms proxy data

Action Item # 5:Assessment of MSPPS Algorithms With ATMS Proxy Data

Submitted by: R. Ferraro

Description:Apply the MSPPS algorithms (primarily rain rate and TPW) in MiRS to ATMS proxy data to assess performances of products, and applicability to ATMS sensor.

Lead Organization:STAR

Response:This AI was based on miscommunication and was later withdrawn

Status:CLOSED


Trr action items2

TRR Action Items


Mirs for npp atms cutr entry criteria

MiRS for NPP/ATMS CUTR Entry Criteria

  • Entry # 1 – Review of TRR Report with Action Items, Responses, Status

  • Entry # 2 – Review of the CUTR for MiRS NPP/ATMS in NDE

    • Unit Test Plan

    • Unit Test Results

    • System Test Plan

    • Risks/Actions


Mirs for npp atms cutr exit criteria

MiRS for NPP/ATMS CUTR Exit Criteria

  • Exit # 1 – Code Unit Test Review Report

    • CUTR Report will be compiled and delivered after CUTR

    • CUTR Report to contain:

      • CUTR Presentation

      • Actions

      • Comments


Trr report summary

TRR Report Summary

  • This TRR Report closes the TRR

  • Total of 5 Action Items:

    • At present, 4 of 5 items are closed, 1 remain open

    • 2 CUTR Entry Criteria have been established

    • 1 CUTR Exit Criterion has been established


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR Report

  • UNIT TEST PLAN

  • Unit Test Readiness

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • Risks/Actions

  • Summary and Conclusions

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 3 –

Unit Test Plan

Presented by

C. Grassotti


Unit test plan environment and configuration

Unit Test Plan: Environment and Configuration

  • For all MiRS DAP unit tests the testing environment will be both the STAR Linux servers and the NDE AIX systems

    • STAR Environment: Full end to end test (RDRs to SND/IMG netCDF4) using Platinum-72 (P72 - proxy data in correct format) data set (single and multiple granules); selected visualization. STAR environment configured as expected in NDE.

    • NDE Environment: Testing of several granulesof P72 data independent of DHS

  • For all MiRS QC DAP unit tests the testing environment will be the STAR Linux servers

    • STAR Environment: Full end to end test (Collocation with GFS, Tier-1, Tier-2 QC, e-mail alert and time series). STAR environment is configured as expected in NDE.

  • For testing in STAR, configuration is the same as that used in the daily processing for all other sensors (e.g. f95, C, IDL, and bash scripts)

  • For testing in NDE, configuration is identical.

  • Most detailed results here will be shown from tests in STAR environment

  • However, final SND/IMG output files from all processing steps to be compared against benchmark data produced in STAR test.


Unit test plan configuration in star environment

Unit Test Plan: Configuration in STAR Environment

  • Top level directory listing of MiRS DAP:

  • To create binary executables: cdsrc; make

  • Binary executables

  • Ancillary data

  • Documentation

  • README

  • Bash scripts

  • PCFs

  • Source code


Unit test plan data

Unit Test Plan: Data

Test data will include -

  • Input data:

    • P72 proxy data generated from IDPS (currently 1 orbit 2010-09-06)

    • GFS forecast data (2002-09-06) time shifted to match P72

  • Intermediate and Output data:

    • Data produced by MiRS processing units

  • Image data:

    • STAR: Image maps of select products (intermediate/final) to confirm successful test

  • Benchmark data:

    • STAR/NDE: summary statistics (npoints,mean,variance,min,max) of select EDRs from final output SND/IMG files created in both STAR and NDE environments to be compared


Unit test plan test method sequence

Unit Test Plan:Test Method, Sequence

  • The test method is to run using proxy data in stand-alone mode (single execution of bash script and f95/IDL code) with all the required input/output files defined at the script level.

  • For many steps the upstream input data files are simply the output generated by the previous required Layer 2 MiRS processing unit (e.g. fm→fmsdr2edr)

  • Confirmation of successful test will be determined by:

    • verifying creation of intermediate and output data (file listings)

    • contents of standard output file (accumulated from scripts, f90 code, etc.)

    • MiRS DAP: statistics of intermediate files; comparison with benchmark files produced in both STAR and NDE (final IMG/SND products),

    • QC DAP: examination of NEDT, QC, and BIAS (radiometric) files and alert files, time series PNGs

    • log files, and PSF

    • diagnostic graphical tools (IDL) available in the STAR environment

  • To the extent that the top level scripts, and lower level codes are integrated with one another these unit tests also constitute a test of the overall software system readiness (cf. System Test Plan)


Unit test plan test procedures for mirs dap

Unit Test Plan:Test Procedures for MiRS DAP

  • Go to /home/pub/chrisg/mirs_working_npp_nde/src

    • Type ‘make’

    • Confirm compilation without errors and all binaries in bin/

  • Create working directory in /home/pub/chrisg

    • mkdir wd_npp_p72_01 (for example)

  • Copy PCF and input data to working directory

    • Copy setup/npp_pcf.bash

    • Copy ATMS granule (for example): SATMS_npp_d20100906_t0435407_e0436121_b00003_c20110321195442103526_noaa_ops.h5 and GATMO_npp_d20100906_t0435407_e0436121_b00003_c20110321195442103526_noaa_ops.h5

  • Run driver script scripts/npp_scs_nde.bash <working_directory>

    • Run with one step turned on in the PCF at a time to test each individual unit.

  • Verify output from each step was created successfully

    • Files exist

    • Statistics of data in file

    • Images (if applicable)


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR Report

  • Unit Test Plan

  • CODE UNIT TESTS

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • Risks/Actions

  • Summary and Conclusions

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 4 –

Code Unit Tests

Presented byC. Grassotti – Context and System Layer

C. Grassotti - MiRS DAP

K. Garrett - QC DAP


Software architecture overview

Software Architecture:Overview

  • The software architecture describes the structure of the system software elements and the external and internal data flows between software elements.

  • 3 Layers of design (STAR EPL Guidelines):

    • Context Layer - 0: External Interfaces

    • System Layer - 1: Flow Between Units

    • Unit Layer - 2: Flow Within Units


Mirs context layer external interfaces

MiRS Context Layer:External Interfaces

MiRS External Interfaces

NDE DHS Boundary

Systems

Configurations

Process Req.

NDE Product

Invocation

MiRS/QC

Generation Manager

Return Code

Product

Rule Sets

Generation

Output Files

Input Files

Specifications

& PSF

& PCF

Working

Directory

PSF (MiRS output)

Output

Working Directory

PCF (MiRS input)

Forensics

DAP

Repository

Specifications

Product Files

SAN

NDE Distribution Server

Input Files

(HDF5,

GRIB)

GFS (GRIB)

GDAS (GRIB)

Data Areas

NWP not necessary for Core Products (QC only)

IDPS

ESPC

ECMWF(GRIB)

Configurations Info

Input (HDF5) Files

MIRS System

DDS

NDE Production Manager

1


Mirs external interfaces

MiRS External Interfaces

  • File format requirements for NPP ATMS

    • ATMS level 1b granules/geo formatted in HDF5

    • PCF ascii file generated by NDE DHS

    • MiRS product outputs formatted in netCDF4 (CF conventions)

    • MiRS output PSF ascii file listing output files

    • MiRS readers and encoders support these formats and have been tested in NDE

  • Metadata:

    • Current MiRS Collection Level metadata available in ISO 19115 at CLASS (for POES/Metop/DMSP)

    • Expectation is for a similar Collection Level file for MIRS NPP ATMS products to be stored at CLASS

    • Metadata requirements for MiRS NPP ATMS will be outlined by updated Submission Agreement in the future

    • MiRS NPP ATMS Granule Level metadata to be contained inside the MiRS netCDF4 output header (following STAR metadata template finalized 5/18/2011)


Mirs system layer processing units

MiRS System Layer: Processing Units

  • Each major step in the MiRS processing sequence is a stand-alone bash script and a corresponding Fortran 95 executable and namelist file and constitutes a Layer-2 Test Unit


The mirs system layer npp scs nde bash

The MiRS System-Layer:npp_scs_nde.bash

  • Some or all units in the system layer may be invoked by the top level driver script npp_scs_nde.bash(in operations all 9 units run from same invocation of driver script).

  • The system layer is where NDE will invoke the MiRS software units.

  • Each unit is a bash script-function that drives a low-level fortran processing program.

  • When the system’s input data is available (ATMS granule), the NDE PGM will run the top level driver script.

    • Execute npp_scs_nde.bash passing the “working directory” path as the argument

    • The NDE PGM will generate a Process Configuration File (PCF) which contains all input file locations and parameters required for processing, and is read in by the driver script.

  • All code units process sequentially, one ATMS granule at a time.

  • The NDE DHS must be able to run multiple instances of these units to process concurrently available granules.

  • Each instance will produce a PSF file containing a list of output product files if they were created successfully.

  • In STAR, the driver script may be invoked through crontab or run manually and the PCF variables are specific to the STAR environment.


Mirs system layer process flow nde environment

MiRS System-Layer Process Flow: NDE Environment

npp_scs_nde.bash

Log File

Return value to PGM

Local Processing Directories

PGM

d

L1B Sensor Data

TDRs

rdr2tdr

(HDF5)

TDRs

L1B Sensor Data (HDF5)

tdr2sdr

SDRs

PCF

SDRs

fm

FMSDRs

FMSDRs

chopp

Chopped FMSDRs

Local Processing Directories

(working directory)

Chop FMSDRs

applyRegress

REGRESS Retr

Chopped FMSDRs

fmsdr2edr

EDRs

NDE

SAN

EDRs

mergeEdr

Merged EDR

EDRs + Ancillary`

vipp

DEPs

EDRs + DEPs

mirs2nc

SND (netCDF4 EDR)

IMG (netCDF4 DEP)

Process Status File


Unit test results mirs dap

Unit Test Results: MiRS DAP


Mirs unit tests star environment

MiRS Unit Tests: STAR Environment

  • Run on standard Linux machine (e.g. orbit272L)

  • Codes precompiled using Linux compiler (ifort, HDF5, netCDF4)

  • Required:

    • Working directory (in NDE this will be created at run time by the PGM): this is where all file input/output takes place

  • Working directory contents:

    • Single ATMS granule: 2 HDF5 files containing geolocation (GATMO_*.h5) and radiometric data (SATMS_*.h5)

    • PCF: contains directory, variable specifications, flags to control execution of MiRS script (npp_scs_nde.bash), which steps to run, etc.


Mirs unit tests star environment1

MiRS Unit Tests: STAR Environment

  • In operations all processing steps will be run in same invocation of npp_scs_nde.bash

  • For unit tests script will be run multiple times with only the testing unit step turned on

    • Advantage: tests both the underlying processing software, as well as top level invocation scripts

  • Working directory is sole argument to bash script

  • Unit tests will be performed with P72 proxy data valid on 2010-09-06


Mirs unit tests star environment2

MiRS Unit Tests: STAR Environment

  • Example showing initial listing of working directory before first invocation of bash script

    • Test ATMS granule: SATMS_npp_d20100906_t0435407_e0436121_b00003_c20110321195442103526_noaa_ops.h5 and GATMO_npp_d20100906_t0435407_e0436121_b00003_c20110321195442103526_noaa_ops.h5

  • Geolocation File

  • PCF

  • Radiometric File

  • At NDE, the working directory and its contents are created by the DHS each time a new granule is available for processing

  • File naming and format convention for simulated data identical to real data


Mirs unit tests star environment3

MiRS Unit Tests: STAR Environment

  • Example showing process switches portion of PCF:

  • Steps turned on


Mirs unit tests star environment4

MiRS Unit Tests: STAR Environment

  • Example showing paths portion of PCF:

  • Working directory

  • Root path (location of MiRS DAP)


Mirs unit tests

MiRS Unit Tests

  • The following will be presented for each of the 9 units:

    • Unit Description : Purpose and Function

    • Test Sequence/Results


Unit rdr2tdr purpose and function

Unit rdr2tdr: Purpose and Function

  • Convert raw sensor data records to temperature data records (antenna temperatures)

  • Reformatted into MiRS internal format

  • Computessensorradiometric noise values (used to update the instrument noise matrix used in the 1dvar minimization)

  • Input: Level 1b in HDF5 format produced by external process at NDE (current testing with proxy data generator uses HDF5). For NPP ATMS, the Level 1b data may be actual TDRs or SDRs, rather than RDRs.

  • Output: TDR and NEDT files in internal format produced by rdr2tdr

  • It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs_nde.bash)


Unit rdr2tdr test sequence script invocation

Unit rdr2tdr Test Sequence –Script invocation

  • Step 1: Example showing invocation of bash script (same for subsequent unit tests)

  • Working directory

  • Bash script


Unit rdr2tdr test sequence working directory listing

Unit rdr2tdr Test Sequence –Working Directory Listing

  • Step 2: Listing of working directory after invocation of bash script

  • NEDT file created (needed for QC DAP)

  • TDR file created


Unit rdr2tdr test sequence standard output

Unit rdr2tdr Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • working directory

  • Output confirms successful completion of rdr2tdr


Unit rdr2tdr test sequence statistical summary of output file contents

Unit rdr2tdr Test Sequence –Statistical summary of output file contents

  • Step 4: IDL utility scans TDR file and outputs basic statistics of TDRs in output file showing values within physically realistic limits

  • Channel

  • Nobs

  • Mean

  • Stdev

  • Min

  • Max


Unit tdr2sdr purpose and function

Unit tdr2sdr: Purpose and Function

  • Apply antenna pattern correction (if selected) to convert tdr files to sensor data record (TBs or radiances)

  • In operations, no correction applied and the step is simply a reformatting to MiRS internal format (differences accounted for in radiometric bias corrections)

  • Input: TDR files in internal format produced by rdr2tdr

  • Output: SDR files in internal MiRS format

  • It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs_nde.bash)


Unit tdr2sdr test sequence working directory listing

Unit tdr2sdr Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

  • MiRS formatted SDR file created


Unit tdr2sdr test sequence standard output

Unit tdr2sdr Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms successful completion of tdr2sdr


Unit tdr2sdr test sequence statistical summary of output file contents

Unit tdr2sdr Test Sequence –Statistical summary of output file contents

  • Step 4: IDL utility scans SDR file and outputs basic statistics of TBs in output file showing values within physically realistic limits

  • Channel

  • Nobs

  • Mean

  • Stdev

  • Min

  • Max


Unit fm purpose and function

Unit fm: Purpose and Function

  • Footprintmatching to ensure all channelsview the same location on the Earth

  • Three options:

    • Use fm code (to beavailablefrom IPO) to tailorresolution to available CPU resources and requirements (Best option)

    • Use resampled data from IDPS (stepwouldthenbe a simple copy)

    • MiRSheritage code: FOV averaging; used for this unit test

      • High resolution: 12 scanlines per granule, 96 FOVs per scanline, 1152 FOVs per granule. Each channel measurement retains its value for each FOV

      • Low resolution: 3x3 average for each FOV at each channel (3 FOVs x 3 scanlines), 32 FOVs per scanline

  • Input: SDR files produced by tdr2sdr

  • Output: Footprint-matched SDRs (FMSDRs) in the MiRS internal RAD file format and NEDT file

  • It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs_nde.bash)


Unit fm test sequence working directory listing

Unit fm Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

  • FMSDR file created


Unit fm test sequence standard output

Unit fm Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms successful completion of tdr2sdr


Unit fm test sequence statistical summary of output file contents

Unit fm Test Sequence –Statistical summary of output file contents

  • Step 4: IDL utility scans FMSDR file and outputs basic statistics of TBS in output file showing values within physically realistic limits

  • Channel

  • Nobs

  • Mean

  • Stdev

  • Min

  • Max

Footprint averaging: NPOINTS=1152/(3x3)=128


Unit chopp purpose and function

Unit chopp: Purpose and Function

The choppstepallows for the simultaneousretrieval of multiple sub-orbits or sub-granules derivedfrom the input file

Choppingdivides the orbit or granule FMSDR files into X number of files, where X isdefined in the PCF

Input: FMSDR files produced by fm step

Output: Chopped FMSDRs

It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs.bash)

Note: This step is optional, and may be configured to optimize the efficiency of the processing environment and take advantage of unused resources.

57


Unit chopp test sequence working directory listing

Unit chopp Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

10 Chopped SDR files created from initial FMSDR


Unit chopp test sequence standard output

Unit chopp Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms successful completion of chopp


Unit chopp test sequence statistical summary of output file contents

Unit chopp Test Sequence –Statistical summary of output file contents

  • Step 4: IDL utility scans CHPDR files and outputs basic statistics of TBs in output file showing values within physically realistic limits

  • Nobs

  • Mean

  • Stdev

  • Min

  • Max

  • Channel

  • Chopping: NPOINTS=128/10=12


Unit applyregress purpose and function

Unit applyRegress: Purpose and Function

  • First guessgeneration (optional)

  • Needed to start 1dvar minimization (iterative)

  • Estimate of the geophysical state vector (T,q, Tskin, Emis, etc.) neededateachfmsdr location

  • applyRegress: Regression (using real observed TBs based on off-line training)

  • Input: FMSDR (or chopped FMSDR) files, tuning files, covariance matrix files, bias correction files, modeling error file, topography file

  • Output file format: Same as EDR Scene files (internal MiRS)

  • It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs_nde.bash)


Unit applyregress test sequence working directory listing

Unit applyRegress Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

10 Chopped REGRESS files created from 10 chopped FMSDR files


Unit applyregress test sequence standard output

Unit applyRegress Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms successful completion of applyRegress


Unit fmsdr2edr purpose and function

Unit fmsdr2edr: Purpose and Function

  • 1dvar: converts footprint matched SDRs to EDRs (MiRS core products)

  • All elements of geophysical state vector retrieved simultaneously: T(p), q(p), Tskin, Emis, CW(p), RW(p), IW(p)

  • Variational solution optimal assuming error characteristics of geophysical background, forward model (CRTM), sensor NEDT, and Jacobians (derivatives) obtained from forward model

  • Tuning file can adjust characteristics of retrieval (nEOFs, channels used, etc.)

  • QC flags assigned to each EDR location

  • Input: FMSDRs (MiRS RAD file format) produced by fm code (or chopped FMSDRs), tuning files, NEDT file, first-guess, covariance matrix files, CRTM files, bias correction files, modeling error file, topography file

  • Output: EDR Scene files (internal MiRS)

  • It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs.bash)


Unit fmsdr2edr test sequence working directory listing

Unit fmsdr2edr Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

10 EDR files (MiRS internal format) produced from 10 chopped FMSDR files


Unit fmsdr2edr test sequence standard output 1 2

Unit fmsdr2edr Test Sequence –Standard output (1/2)

  • Step 3: portion of standard output produced

  • Output confirms processing of 10 CHPDR files


Unit fmsdr2edr test sequence standard output 2 2

Unit fmsdr2edr Test Sequence –Standard output (2/2)

  • Step 3: portion of standard output produced (single chopped FMSDR file)

  • Output confirms successful processing of all chopped files


Unit mergeedr purpose and function

Unit mergeEDR: Purpose and Function

The mergeEDRstep combines all sub-orbit or sub-granule retrieval (EDR) files back into 1 file, if choppingwasapplied.

X files are mergedtogether, where X isdefined in the PCF

Input: EDR files produced by fmsdr2edr step

Output: 1 Merged EDR file

It reads in a namelist which specifies operating parameters (passed from the PCF by npp_scs.bash)

Note: This step is optional, and may be configured to optimize the efficiency of the processing environment and take advantage of unused resources. Must be enabled if the chopping step is applied.

68


Unit mergeedr test sequence working directory listing

Unit mergeEDR Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

Single EDR file created from merging 10 chopped EDR files (MiRS internal format)


Unit mergeedr test sequence standard output

Unit mergeEDR Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms merging into a single EDR file


Unit mergeedr test sequence statistical summary of output file contents

Unit mergeEDR Test Sequence –Statistical summary of output file contents

  • Step 4: IDL utility scans single merged EDR file and outputs basic statistics of select products in output file showing values within physically realistic limits


Unit vipp purpose and function

Unit vipp: Purpose and Function

  • Post-processing converts EDRs to derived environmental parameters (DEPs)

  • Two types of processing:

    • 1. Vertical Integration:

      • q(p) → TPW, CL(p) → CLW, RW(p) → RWP, IW(p) → IWP

    • 2. Post-processing:

      • Rain Rate: Regression RR=f(CLW,RWP,IWP)

      • Sea Ice Concentration (FY,MY): Look-up in emissivity catalogs

      • Snow Water and Grain Size: Minimized cost function (emissivity LUT based on CRTM physical snow emissivity model, uncertainties in SW and GS).

  • Input: EDR Scene files produced by fmsdr2edr or mergeEDR (internal MiRS)

  • Output: DEP (Derived product) file (internal MiRS)

  • It reads a PCF, writes a PSF, and returns error handling information to the calling NDE Data Handling System (via npp_scs.bash).


Unit vipp test sequence working directory listing

Unit vipp Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

Single DEP (MiRS internal format) file created from processing EDR file


Unit vipp test sequence standard output

Unit vipp Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms successful creation of DEP file


Unit vipp test sequence statistical summary of output file contents

Unit vipp Test Sequence –Statistical summary of output file contents

  • Step 4: IDL utility scans DEP file and outputs basic statistics of select products in output file showing values within physically realistic limits


Unit convertmirs2nc purpose and function

Unit convertMirs2nc: Purpose and Function

  • Converts EDR and DEP files from MiRS internal binary to netCDF4 format

  • Input: EDR from fmsdr2edr output

  • Input: DEP from vipp output

  • Output: SND and IMG product files in netCDF4 format


Unit convertmirs2nc test sequence working directory listing

Unit convertMirs2nc Test Sequence –Working Directory Listing

  • Step 1: npp_scs_nde.bash script invocation (as before)

  • Step 2: Listing of working directory after invocation of script

  • 2 netCDF files (SND,IMG) created from original EDR and DEP files

  • PSF created (required for NDE)


Unit convertmirs2nc test sequence standard output

Unit convertMirs2nc Test Sequence –Standard output

  • Step 3: portion of standard output produced

  • Output confirms successful creation of SND and IMG files (in netCDF4 format)


Unit convertmirs2nc statistical summary of output file contents

Unit convertMirs2nc–Statistical summary of output file contents

IMG

  • Step 4: IDL utility scans SND and IMG files and outputs basic statistics of select product in output file showing values within physically realistic limits

SND

EDR

DEP

  • Step 5: IMG/SND statistics very close to EDR/DEP


Unit convertmirs2nc precision requirements for netcdf output

Unit convertMirs2nc–Precision Requirements for netCDF Output

  • Differences in statistical summaries between EDR/DEP and SND/IMG due to scaling applied when writing to *.nc files

  • Currently using OSPO defaults; Consider modifications for improved efficiency (file size) and precision where needed

  • Selected Products with Suggested Changes

  • * Other variables such as Lat,Lon, currently stored as float(4) etc. might also be considered


Mirs system layer test sequence psf generation

MiRS System Layer Test Sequence –PSF Generation

  • PSF required for operations in NDE; Contains listing of all files produced that require registration with the PGM

  • npp_scs_nde.bash script generates PSF as final step (only if fmsdr2edr and vipp steps run)

  • Listing of working directory after invocation of script:

PSF created (required for NDE)


Mirs system layer test sequence psf contents

MiRS System Layer Test Sequence –PSF contents

  • Upon completion of script, confirmation that PSF contents are in the required format and contain all required files: SND,IMG, FMSDR, EDR, DEP, nedt


Mirs unit tests end to end testing and multiple granules

MiRS Unit Tests –End to end testing and multiple granules

  • End to end testing by simply turning on all processing steps

  • Multiple granules:

    • Single granule contains only 32 sec of data (1152 profiles at high res, 128 profiles at low res 3x3 averaging), not sufficient for qualitative visualization

    • Tested in STAR environment using 20 successive granules of P72 simulated data (high-resolution mode) valid 2010-09-06 (total time ~ 10.5 min)

  • Visualization with MiRS IDL software used in STAR daily processing for other sensors


Mirs unit tests end to end testing and multiple granules1

MiRS Unit Tests –End to end testing and multiple granules

CHISQ

NATTEMPTS

QC

NITER


Mirs unit tests end to end testing and multiple granules2

MiRS Unit Tests –End to end testing and multiple granules

T500

WV850

TSKIN

EM31


Mirs unit tests end to end testing and multiple granules3

MiRS Unit Tests –End to end testing and multiple granules

TPW

CLW

RWP

IWP


Mirs unit tests end to end testing and multiple granules4

MiRS Unit Tests –End to end testing and multiple granules

  • End to end testing in STAR environmentwith multiple granules, followed by visualizing retrieved SND and IMG products confirms that the system is producing stable, physically reasonable values

  • Since P72 test data are simulated, absolute validation not possible


Mirs unit tests nde environment

MiRS Unit Tests –NDE Environment

  • Run on IBM-AIX server: n05apn5 (AIX 6.1)

  • Codes precompiled using AIX compiler (xlf95)

  • End to end testing in NDE environmentwith a single granule (high resolution)

  • Directory listings and standard outputs to confirm steps run to completion (not shown)

  • Final SND*.nc and IMG*.nc files compared with those produced in STAR environment

  • Granule used for comparison: SATMS_npp_d20100906_t0500127_e0500441_b00003_c20110321195442292903_noaa_ops.h5

  • netCDF4 files compared:

    • NPR-MIRS-SND_v7_NPP_s20100906050012_e20100906050044_c*.ncand

    • NPR-MIRS-IMG_v7_NPP_s20100906050012_e20100906050044_c*.nc


Mirs unit tests nde environment1

MiRS Unit Tests –NDE Environment

  • Comparison of SND/IMG *.nc files on NDE with those on STAR show identical contents

  • netCDF4 files compared:

    • NPR-MIRS-SND_v7_NPP_s20100906050012_e20100906050044_c*.ncand

    • NPR-MIRS-IMG_v7_NPP_s20100906050012_e20100906050044_c*.nc


Mirs unit tests summary

MiRS Unit Tests –Summary

  • Used P72 simulated data throughout

  • Run in STAR environment on single and multiple granules

  • Run in NDE on single granule

  • STAR: Comparison of individual unit I/O for successful completion

  • STAR/NDE: Comparison of final SND and IMG products to confirm consistency between computing environments

  • All tests were successful:

    • all units run individually and together to completion

    • no error messages

    • values stable and within realistic limits

    • STAR and NDE *.nc files consistent


Unit test results qc dap

Unit Test Results: QC DAP


Mirs qc overview

MiRS QC Overview

  • Overall Objective:Comprehensive real-time monitoring at various stages of MIRS data processing; selective flagging and notification of anomalies via e-mail

  • Run daily in STAR environment; Applied to N-18, N-19, Metop-A, NPP/ATMS, DMSP

  • Tier-1 (“Autonomous”) QC:Easily implemented in operations

    • NEDT monitoring (time series, e-mail alerts)

    • QC flag monitoring (time series, e-mail alerts)

    • Convergence monitoring (1dVAR) (time series, e-mail alerts)

  • Tier-2 (“Intermediate”) QC:

    • Radiometric performance (time series, e-mail alerts for dynamic biases)


Qc system layer processing units

QC System Layer : Processing Units

  • Each step in the MiRS Tier-1 and Tier-2 QC processing sequence is a stand-alone bash script and one or more corresponding Fortran 95 executables, or IDL procedures (v6) driven by namelist files


Mirs tier 1 and 2 qc system layer process flow nde environment

MiRS Tier-1 and 2 QC System-Layer Process Flow: NDE Environment

T1

E-Mail if threshold exceeded

NEDT (rdr2tdr)

qcNedt (T1)

Local Processing Directories

T2

E-Mail if thresholds exceeded

d

QC (fmsdr2edr)

qcRetrieval (T1)

DDS

GFS (GRIB)

prepNwp (external)

GFS (deGRIBed)

Local Processing Directories

FMSDR`(fm)

nwp (T2)

NWP

GFS (deGRIBed)

NWP

fwd (T2)

Unless specified, all formats are MiRS internal

FWD

FMSDR (fmsdr2edr)+FWD

biasGen (T2)

biasCorr

E-Mail if threshold exceeded

biasCorr

Local Processing Directories

qcRadiometricBias (T2)

Time series radiometric bias (*.png)

biasCorr

biasMonitor (T2)

Time series qc, conv, nedt (*.png)

NEDT (rdr2tdr)+QC (fmsdr2edr)

dataQualityMonitor (T1)

npp_qc_nde.bash

NB: Time series require archivingbiasCorr, NEDT and QC files


Qc dap unit tests star environment

QC DAP Unit Tests: STAR Environment

  • Run on standard Linux machine

  • Mix of IDL and F95: codes precompiled using Linux compiler (ifort)

  • Same paradigm as MiRS DAP: temporary working directory in which all I/O takes place

  • MiRS DAP must have already been run on current granule!

  • Required (minimum 19 files):

    • Previous granule(s): Bias file, Nedt file, QC file (for time series)

    • Current granule: Nedt, FMSDR, EDR, DEP,SATMS

    • Nominal Bias file (copied from MiRSSemiStaticData)

    • GFS forecast files deGRIBed by prepNWP (normally 5 atm + 5 sfc)

    • PCF: contains directory, variable specifications, flags to control execution of MiRS script (npp_qc_nde.bash), which steps to run, etc.


Qc unit test plan test procedures for qc dap

QC Unit Test Plan:Test Procedures for QC DAP

  • Go to /home/pub/chrisg/mirs_qc/src

    • Type ‘make’

    • Confirm compilation without errors and all binaries in bin/

  • Create working directory in /home/pub/chrisg

    • mkdir qc_d20100906_t0500447_e0501161_04 (for example)

  • Two high-resolution granules processed (minimum 2 needed for time series):

    • d20100906_t0435407_e0436121

    • d20100906_t0500447_e0501161

  • Copy PCF and input data to working directory

    • Copy setup/npp_pcf.bash

    • Copy ATMS granule and other required files (minimum of 19, see previous slide)

  • Run driver script script/npp_qc_nde.bash <working_directory>

    • All steps will be run in sequence

  • Verify output from each step was created successfully

    • Files exist, and their contents (where applicable)

    • E-mail alerts

    • Time series images


Qc dap unit tests star environment1

QC DAP Unit Tests: STAR Environment

  • Example showing initial listing of working directory before first invocation of npp_qc_nde.bash script:

  • BIAS (previous and nominal)

  • DEP

  • FMSDR

  • GFS Data

  • NEDT (previous and current granule)

  • PCF

  • QC (previous granule)

  • Original Granule

  • At NDE, the working directory and its contents are created by the DHS each time a new granule is available for processing


Qc dap unit tests star environment2

QC DAP Unit Tests: STAR Environment

  • Example showing process switches portion of QC PCF:

  • Additional switches located in main driver script

  • Steps turned on


Qc dap unit tests star environment3

QC DAP Unit Tests: STAR Environment

  • Example showing invocation of bash script:

  • Working directory

  • Bash script


Qc dap test sequence results

QC DAP Test Sequence/Results

  • Standard Output from npp_qc_nde.bash indicates all steps run to completion

  • NWP step

  • FWD step

  • BIAS step

  • Retrieval QC

  • NEDT QC

  • Radiometric Bias QC

  • QC and NEDT Time Series

  • Radiometric BiasTime Series


Qc dap test sequence results1

QC DAP Test Sequence/Results

  • Upon completion of running npp_qc_nde.bash, partial directory listing indicates all necessary files have been created:

  • Bias QC

  • Radiometric BiasTime Series

  • Ret QC Time Series

  • NEDT Time Series

  • NEDT QC

  • Retrieval QC

  • PSF

  • Text Files with QC Information (needed for e-mail)


Qc dap retrieval qc results qc file and checkresult file

QC DAP Retrieval QC Results –QC File and _checkResult File

  • QC_MONS_* file to be archived and used in subsequent runs of QC DAP

  • qcRetrieval_checkResult created only when levels exceed threshold: used to generate e-mail

  • The values indicate that the rate of QC=0 was 67.45%, which is below the current threshold of 70%; therefore an e-mail alert is generated


Qc dap retrieval qc results e mail alert generation

QC DAP Retrieval QC Results –E-Mail Alert Generation

  • E-Mail Alert:


Qc dap nedt qc results npp nedt file and qcnedt txt file

QC DAP NEDT QC Results –npp_nedt_ File and qcNedt.txt File

  • npp_atms_nedt_* file to be archived and used in subsequent runs of QC DAP

  • qcNedt.txt created only when levels exceed threshold, or if one or more channels turned off (Tuning File): used to generate e-mail

  • The message indicates that channels 7 and 8 were turned off during processing; therefore an e-mail warning is generated


Qc dap nedt qc results e mail alert generation

QC DAP NEDT QC Results –E-Mail Alert Generation

  • E-Mail Alert:


Qc dap radiometric qc results biascorrec npp file and qcradiometricbias txt file

QC DAP Radiometric QC Results –biasCorrec_npp_ File and qcRadiometricBias.txt File

  • biasCorrec_npp_* file to be archived and used in subsequent runs of QC DAP

  • qcRadiometricBias.txt created only when difference between computed (dynamic) and operational (static) bias exceeds 5 times nominal channel nedt: used to generate e-mail

  • The message indicates that these thresholds were exceeded; therefore an e-mail warning is generated (large file)


Qc dap radiometric qc results e mail alert generation

QC DAP Radiometric QC Results –E-Mail Alert Generation

  • E-Mail Alert:


Qc dap nedt qc results time series generation

QC DAP NEDT QC Results –Time Series Generation

  • Time series with two points (granules):

  • These granules were selected to be ~ 25 minutes apart, but in operations each granule will be only ~32 secs long

  • Need guidance from NDE on scenario for time series generation (frequency of generation, time difference between granules, etc.)


Qc dap retrieval qc results time series generation

QC DAP Retrieval QC Results –Time Series Generation

  • Time series with two points (granules):

  • Convergence Rate

  • QC=1 Percentage


Qc dap radiometric qc results time series generation

QC DAP Radiometric QC Results –Time Series Generation

  • Time series with two points (granules):


Qc dap results psf generation

QC DAP Results –PSF Generation

  • As required for NDE, a PSF is created upon completion of the driver script (this can be tailored, by adding *.png files, etc.):


Mirs qc unit tests summary

MiRS QC Unit Tests: Summary

  • STAR Environment: MiRSQC DAP run end to end in STAR environment on 2 P72 granules utilizing outputs from MiRS DAP

    • Examination of outputs: text, e-mail warnings and final *.png to confirm successful completion

  • NDE Environment: not run since test environment is similar (Linux) and not integrated with the DHS; e-mail generation or alerting function TBD; To be implemented in System Test

  • MiRS IPT to work with NDE to facilitate integration effort; NDE should include specification of scheduling scenarios for QC DAP


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR Report

  • Unit Test Plan

  • Code Unit Tests

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • SYSTEM TEST PLAN

  • Risks/Actions

  • Summary and Conclusions

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 5 –

System Test Plan

Presented by

K. Garrett


Systemtest plan environment and configuration

SystemTest Plan: Environment and Configuration

  • Environment: NDE Computing environment (Linux, AIX)

  • Tests:

    • MiRS DAP: Testing of multiple granules of P72 proxy data interfaced with DHS

    • QC DAP: Testing of of multiplegranules of P72 proxy data independent of DHS; Testing of at least 2 granules of proxy data interfaced with DHS; include e-mail initiation (if desired), GFS access (prepNWP), and graphical output

  • Configuration: identical to that presented at CUTR

    • Context Layer: Interfaced with DHS

    • System Layer: bash script (npp_scs_nde.bash, npp_qc_nde.bash)

    • Unit Layer: all code units (bash, Fortran90, IDL, C) presented


Systemtest plan data

SystemTest Plan: Data

  • Test data will include:

    • P72 proxy data generated from IDPS (currently 1 day 2010-09-06)

  • Image data:

    • QC DAP time series only

  • Benchmark data:

    • SND/IMG files created in both STAR and NDE environments to be compared

  • Truth data:

    • NWP forecasts/analyses from GFS/GDAS (QC DAP only)


Systemtest plan test method sequence

SystemTest Plan:Test Method, Sequence

  • The test method is to run end to end, including interfacing with DHS

  • Goal is to have MiRS DAP run on multiple granules followed by QC DAP, all driven by system scheduler

  • Confirmation of successful test will be determined by:

    • contents of standard output file (accumulated from scripts, f90 code, etc.)

    • comparison with benchmark files produced in both STAR and NDE (final IMG/SND products),

    • log files, and PSF

    • graphical outputs produced by QC DAP

    • diagnostic graphical tools (IDL) available in the STAR environment (ftp product files back to STAR)

  • The Code Unit Review presented here already included elements of a System Test, thereby reducing risk


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR Report

  • Unit Test Plan

  • Code Unit Tests

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • RISKS/ACTIONS

  • Summary and Conclusions

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 6 –

Risks and Actions

Presented by

K. Garrett


Open cdr risks

Open CDR Risks

  • Risk #1: Unclear if resources available to run MiRSQC DAP in high-resolution mode.

    • Risk Mitigation:Workload scenarios at NDE can determine resource adequacy for MiRS NPP/ATMS. NDE to develop/clarify scenarios for QC DAP.

    • Status:Open (but risk for MiRS DAP is considered reduced, based on high-resolution testing on Linux platforms at STAR, and planned resources at NDE)

  • Risk #2: NPP launch date may be postponed beyond Oct 2011; Budget planning assumes minimal schedule slippage.

    • Risk Mitigation:Project lead to monitor schedule vis-à-vis MiRS project plan for FY10 and FY11 and, if needed, request additional funding in consultation with MiRS Oversight Board via Annual Review for Satellite Product Development

    • Status: Open


Open cdr risks1

Open CDR Risks

  • Risk #3: Footprint Matching (FM) codes not integrated

    • Risk Mitigation: (1) Use resampled data from IDPS; (2) Expected that MiRS will process highest resolution data available and can do simple FOV averaging.

    • Status: Open (BG MatLab code obtained from IPO; significant LOE required to integrate with MiRS once FM code is obtained)

  • Risk #4: Proxy data fidelity; Preclassifier and post-processing algorithms partially dependent on calibration with proxy (or real) data.

    • Risk Mitigation: MiRS performing well with current nominal values and parameters. Calibration and tuning to be performed immediately post-launch.

    • Status: Open


Open cdr risks2

Open CDR Risks

  • Risk #5: SciTech Renewal

    • Risk Mitigation: MiRS IPT expected to remain in place during any transition. Project will have advance notice and can reallocate resources as necessary to maintain continuity. Funding for current contract tasks through 2011.

    • Status: Open


Open trr risks

Open TRR Risks

  • Risk #1: Simulated data and format may not represent actual NPP/ATMS data (also a CDR risk)

    • Risk Mitigation:Testing will utilize and P72 proxy data (official) to ensure consistency, as those should be the true data formats (CDFCB).

    • Status:Closed (testing for CUTR utilized P72 exclusively)

  • Risk #2: Coefficient files require real data for training and algorithm tuning (bias, covariances, first-guess, catalogs) (also a CDR risk)

    • Risk Mitigation:Post-launch efforts will focus on cal/val; software and correction coefficients based on proxy data already in place, which is adequate for testing purposes.

    • Status: Open


Open trr risks1

Open TRR Risks

  • Risk #3: Available resources in STAR and NDE environments are not consistent (IDL versions, compiler versions, etc.)

    • Risk Mitigation:Identify and address issues during the code unit testing. Efforts have already been taken to ensure MiRS software is compatible with a variety of operating environments (Linux, AIX, multiple compilers).

    • Status: Open

  • Risk #4: QC DAP lacks ability to monitor radiometric bias for upper-atmospheric ATMS temperature sounding channels using GFS at input. GFS model profiles only extend to 10 mb, below the sensitivity of ATMS channels 14 and 15 (57 GHz).

    • Risk Mitigation:Broader instrument issues will be captured through NEDT, QC, or radiometric monitoring of other ATMS channels. STAR will also perform radiometric monitoring using other data sources which extend to the upper atmosphere where ATMS channels 14 and 15 are sensitive (e.g. ECMWF analysis).

    • Status: Open


Trr action items3

TRR Action Items


Review items summary

Review Items Summary

  • 5 Risk Items from the CDR were reviewed, 5 of which are still open

  • 5 Action Items from the TRR were identified, 5 are closed

  • 4 TRR Risk Items were reviewed, 4 remain open; (NB: 2 are already contained in CDR risks)

  • 0 CUTR Risk Items were identified


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR Report

  • Unit Test Plan

  • Code Unit Tests

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • Risks/Actions

  • SUMMARY AND CONCLUSIONS

  • Discussion


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

Section 7

Summary and Conclusions

Presented byK. Garrett


Summary and conclusions

Summary and Conclusions

  • Following have been reviewed:

    • TRR Report

    • Unit Test Plan

    • Code Unit Test Results

    • System Test Plan

    • Risks and Actions


Next steps

Next Steps

  • Prepare CUTR Report (including action items)

  • Reviews:

    • System Readiness Review in January, 2012 [9.1.5 in Level 1 Reqs Doc ]

  • Update Documentation following SPSRB Guidelines

  • Follow ESPDS Guidelines for MiRS DAP and QC DAP (documentation, software, test data)

  • Address action items identified in CUTR


Microwave integrated retrieval system for npoess preparatory project mirs npp atms integration into nde code unit test review may 26 2011

  • Introduction

  • TRR Report

  • Unit Test Plan

  • Code Unit Tests

    • Code Unit Tests of Individual Units: MiRS DAP and QC DAP

  • System Test Plan

  • Risks/Actions

  • Summary and Conclusions

  • DISCUSSION


Open discussion

Open Discussion

  • The review is now open for discussion


Back up slides

Back-up Slides


Mirs official products

MiRS Official Products


Mirs anticipated atms hi res processing

MiRS: Anticipated ATMS Hi-Res Processing

Benchmarks based on current processing capacity

  • *Based on:

  • 1 granule = 1152 profiles

  • 1 orbit = 195 granules

  • MiRS Outputs: 22 MB

  • 0.0028 sec/profile

Note: MiRS can distribute processing over multiple CPUs on same node (chopping or not)

Actual

Estimated


  • Login