Pre‐Launch to Post‐Launch Transition and Evaluation of CrIMSS EDR Algorithm and Productsg

Murty Divakarla1, C.D. Barnet2, M. Goldberg2, D. Gu3, X. Liu4, Tom King5 , W Bl k ll6 X Xi 1 E M dd 5 N R N lli1 A G b 5W. Blackwell6, X. Xiong1, E. Maddy5 , N.R. Nalli1, A. Gambacorta5 , 

G. Guo1, X.L. Ma3, S. Kizer4, H.Xie1, and K. Zhang5 

1IM S t G I R k ill MD1IM Systems Group Inc., Rockville, MD  2STAR, NOAA/NESDIS, Camp Springs, MD 

3Northrop Grumman Aerospace Systems, Redondo Beach, CA4NASA Langley Research Center Hampton VA4NASA Langley Research Center, Hampton, VA

5Riverside Technology, inc. ,  MDMIT Linconln Laboratories, MA

Acknowledgements:  Kevin Garrett, Tony Reale, Bomin Sun, and Frank Tilley, STAR/NOAA.

1

Eighth Annual Symposium on Future Operational Environmental Satellite Systems Eighth Annual Symposium on Future Operational Environmental Satellite Systems 9292ndnd AMS Annual Meeting, New Orleans, LA (January 22AMS Annual Meeting, New Orleans, LA (January 22--26), 2012.26), 2012.

PrePre‐‐launchlaunch→→ Post LaunchPost Launch ‐‐ Tailored for Tailored for JPSS KPP Evaluations (AVTP and AVMP)JPSS KPP Evaluations (AVTP and AVMP)

• Objectives» Evaluate CrIMSS EDR Algorithm for Launch–Ready Performance

JPSS KPP Evaluations (AVTP and AVMP)JPSS KPP Evaluations (AVTP and AVMP)

– Official CrIMSS (NGAS/Raytheon) Operational Algorithm EDR Product Assessment with RAOBs/ECMWF

Functional Testing of Operational Data Flow Functional Testing of Operational Data Flow –GRAVITE/IDPS JPSS‐Rehearsal‐II Evaluation of EDR algorithms (Science code, IDPS, Off‐line)

A h• Approach• Coordination of cal/val Activities (STAR/NGAS/LaRC/UW)

• Leverage Existing Capabilities and Utilize Experience Gained Through AIRS and IASI Validation Systems

• Identify Post‐Launch Processes and Exercise with Pre‐Launch Proxy SDR/EDR Products/

• Risk Reduction‐ Consistency in CrIMSS EDR Codes (Science Code, IDPS‐Operations, and Ported off‐line), NOAA‐NUCAPS, MIRS

FirstFirst--Light Light CrIMSSCrIMSS ‘MW‘MW--only’ Retrievalsonly’ RetrievalsUsing ‘the DayUsing ‘the Day--1 Bias Tuning’ 1 Bias Tuning’ -- Day 11/11/2011Day 11/11/2011

Ad t t NOAA/STARAd t t NOAA/STARAdvantages at NOAA/STARAdvantages at NOAA/STAR•CrIMSS Off‐line EDR ALG (Liu and Kizer, LaRC) •Implemented at STARImplemented at STAR

• RTM – OSS•Application Development Library (ADL) availability(ADL) availability

•NUCAPS (Heritage Algorithm – AIRS Science 

h)Team Approach)•Adapted at STAR for AIRS/IASI/CrIS

• RTM – MIT FM•MiRS – MW only Algorithm (Sid Boukabara, Kevin Garrett, Fuzhong Weng, 

3

, g g,Others)

•RTM ‐ CRTM

FirstFirst--Light Light CrIMSSCrIMSS ‘MW‘MW--only’ Retrievalsonly’ RetrievalsUsing SDRs/TDRs, ‘the DayUsing SDRs/TDRs, ‘the Day--1 Bias Tuning’ 1 Bias Tuning’ -- Day 11/11/2011 Day 11/11/2011

Ad t t NOAA/STARAd t t NOAA/STARAdvantages at NOAA/STARAdvantages at NOAA/STAR○ •

□ ■□

◊ X

4Thanks to Kevin Garrett for providing MIRS Bias Tuning, and Antonia for providing NUCAPS Bias tuning

Infrastructure Built to Evaluate CrIMSS EDR Infrastructure Built to Evaluate CrIMSS EDR Products/Functional TestingProducts/Functional Testing (Pre(Pre‐‐Launch)Launch)Products/Functional Testing Products/Functional Testing (Pre(Pre Launch)Launch)

11. Proxy Data Generator Algorithms from LaRC and MITSelect CrIMSS related 

portion and separate unnecessary portion

IDPS OPS code

ING, DMS,  INF,PROInterface to read auxiliary, ancillary,  and SDR data

Layout of CrIMSS EDR Operational Code

» CrIS Proxy – Xu Liu and Kizer» ATMS Proxy  ‐ Bill Blackwell

– Implemented at NOAA/STAR

unnecessary portion(VIIRS, ATMS,  CrIS ….)

Ported CrIMSS OPS code 

JPSS svn repository

NOAA/STAR2.  Product Retrieval Algorithm(s) 

Retrieval Products (EDRs)» NGAS CrIS and ATMS EDR 

CrIMSS Science  CodeInterface to read science code data (F90 codes)

Product Algorithm (off‐line)– Crimss_Larc_v1.5.05, 

Developed by Liu and Kizer– Implemented atImplemented at 

NOAA/STAR» NOAA‐IASI Operational 

Retrievals from NOAA/NESDIS/NUCAPSNOAA/NESDIS/NUCAPS (Gambacorta and many others from STAR)

» Operating at NOAA

Infrastructure Built to Evaluate CrIMSS EDR Infrastructure Built to Evaluate CrIMSS EDR Products/Functional TestingProducts/Functional Testing (Pre(Pre‐‐Launch)Launch)Products/Functional Testing  Products/Functional Testing  (Pre(Pre Launch)Launch)

33. Data Sets for CrIS/ATMS Proxy Data Generation and  NGAS‐CrIMSS EDR Product Evaluation» Focus Day Data Set – IASI/AMSU A/MHS ECMWF GFS RAOBs» Focus Day Data Set – IASI/AMSU‐A/MHS, ECMWF, GFS, RAOBs» Retrieval Evaluations with Global RAOBs, ECMWF, GFS» AEROSE‐2010/2011 (Dedicated RAOBs, ECMWF, GFS)

– Generated and Evaluated at NOAA/STAR (Divakarla AMS 2011)Generated  and Evaluated at NOAA/STAR (Divakarla, AMS, 2011)4.  Evaluation of  CrIMSS EDRs

– With Corresponding IASI/AMSU‐A/MHS EDRs– With ECMWF/RAOBs and IASI EDRsWith ECMWF/RAOBs and IASI EDRs.– JPSS Rehearsal –II,  P‐72 Data Sets

Performed at NOAA/STAR5.Functional Testing of Data Flow from GRAVIGTE/IDPS Operations5.Functional Testing of  Data Flow from GRAVIGTE/IDPS Operations

– Automated Scripts for IDPS SDR/EDR Processing  ‐ P72 Experience/ ADL

– Plans for  ‘on‐request’ Focus‐Day Runs for Special Campaign Events

Post‐Launch Exercise(s) with Pre‐Launch Proxy Data Use of NOAA‐STAR CrIS/ATMS Proxy Data Package

for Bias‐tuning the CrIS/ATMSfor Bias tuning the CrIS/ATMS

1 0 /19 /2 007 - F o cu s D ay G ra nu les - IAS I R e trie va lsC lo u d C lea red an d C lear P erce n tag es

10 0

0

2 5

5 0

7 5

0 20 42 63 83 105

125

146

166

186

208

228

248

G ran u le s S orted fro m S H to N H (G ran u le N u m b e rs A rb itra ry)

(%) A

CC

PCT,

CLR

PCT

AC C P C T C L R P C T

7

PrePre--Launch Launch Validation of CrIMSS EDRs (and IASI EDRs) with ECMWF for Focus Day 10/19/2007N: 22,000 CrIMSS Retrieval Yield: 43%  IASI Yield: 78%,

8

IASI, CrIMSS, ECMWF, RAOBs AnimationFocus Day Matches (10/19/2007)

Validation Tools Developed for Aqua/MetOp are being Adapted to NPP‐CrIMSS

0

50

Latitu

de

RAOB Matches Collocated to Aqua-AIRS and MetOp-IASICollocation Criteria: 3 Hours, and 100 Km Radius

AIRS (1:30 AM/PM) IASI (9:30 AM/PM)

-150 -100 -50 0 50 100 150Longitude

-50

RAOB Matches Collocated to Aqua-AIRS and MetOp-IASICollocation Criteria: 3 Hours, and 100 Km Radius

AIRS (1:30 AM/PM) IASI (9:30 AM/PM)

0

50

Latitu

de

AIRS (1:30 AM/PM) IASI (9:30 AM/PM)

9-150 -100 -50 0 50 100 150Longitude

-50

AEROSEAEROSE‐‐2010/2011 and 2010/2011 and FutureFuture 2012 Campaign Experiments2012 Campaign ExperimentsIASI/ECMWF/NCEPIASI/ECMWF/NCEP‐‐GFS/Dedicated RAOB MatchesGFS/Dedicated RAOB Matchesfor for CrIMSSCrIMSS EDR Evaluation EDR Evaluation ((DivakarlaDivakarla et al., HISE, 2011)et al., HISE, 2011)(( ))

Nalli et al., Poster 500, Wed., Session‐II,12/25, AMS‐2012

04/28/2010 to 05/22/2010

10

CrIMSS EDRs Resilient to Dust? CrIMSS EDRs Resilient to Dust? DustDust‐‐Free and Dusty CrIMSS Retrieval StudyFree and Dusty CrIMSS Retrieval Study‐‐ AEROSEAEROSE‐‐20112011

Future Collaborations with GOCART Future Collaborations with GOCART 

11

‘Dust‐Free ’ vs. ‘Dusty’  Granule Retrievals07/28/2011, 08/01/2011 IASI and CrIMSS

AEROSE‐2011 Matched IASI(RET), ECMWF and CrIMSS (RET) ‐ T(p) Dust‐Free/Dusty

FRE

T vs. ECM

WWF; CrIMSS‐TR

‐TRE

T vs. ECM

W

CrIMSS T(p) CrIMSS T(p) Retrievals Retrievals 

OSE‐2011 IASI‐

are Resilient are Resilient to Dust?to Dust?

NOAA‐A

ERO

CrIMSS EDR Algorithm EvaluationCrIMSS EDR Algorithm EvaluationNOAANOAA‐‐CrIS/ATMS Proxy SDR CrIS/ATMS Proxy SDR 

And Matched Correlative MeasurementsAnd Matched Correlative MeasurementsAnd Matched Correlative MeasurementsAnd Matched Correlative Measurements

Intent: Pre‐Launch evaluation of CrIMSS algorithm and EDR products with RAOB/ECMWF and NOAA‐IASI retrievals (NUCAPS)

Results: Results: The CrIMSS EDR Algorithm performance is  comparable to Heritage Algorithm The CrIMSS EDR Algorithm performance is  comparable to Heritage Algorithm (NOAA(NOAA‐‐IASI  Retrievals) and  shows promise for launch readiness.IASI  Retrievals) and  shows promise for launch readiness.

Helped to develop interfaces to generate matched correlative data sets.Helped to develop interfaces to generate matched correlative data sets.

Helped to develop postHelped to develop post‐‐launch procedures with prelaunch procedures with pre‐‐launch  proxy data.launch  proxy data.

13

p p pp p p p pp p p yp y

Development of  empirical biasDevelopment of  empirical bias‐‐tuning procedures for CrIS/ATMS;  tuning procedures for CrIS/ATMS;  

Unification of statistical routines and testing with common data sets.Unification of statistical routines and testing with common data sets.

PP--72 Proxy Data SDRs/EDR Data Sets72 Proxy Data SDRs/EDR Data Sets(JPSS Rehearsal (JPSS Rehearsal --2 August 182 August 18--21 2011)21 2011)(JPSS Rehearsal (JPSS Rehearsal 2 August 182 August 18 21, 2011)21, 2011)

Intent: Operational  Data Stream Access /Processing from GRAVITE/IDPS , and Functional Testing of Algorithm, Data Flow, Development of Reader/Write Routines, Matched Correlative Data Sets Generation

14

Correlative Data Sets Generation

Results: All the above, + Verification of CrIMSS EDR Products from: IDPS Operations, Results: All the above, + Verification of CrIMSS EDR Products from: IDPS Operations, NGAS:ScienceNGAS:Science Code and Ported OffCode and Ported Off‐‐line Code.line Code.

SummaryyAn array of CrIS/ATMS proxy SDRs and matched EDR products from 

NOAA‐IASI ,  ECMWF/GFS, and RAOB Measurements were used to E l t C IMSS EDR P d tEvaluate CrIMSS EDR Products.» The CrIMSS algorithm shows Reasonable Ability for a Post‐

Launch Performance. I f t t D l d i th P L h Ph h l TInfrastructure Developed in the Pre‐Launch Phase helps To

» Acquire and Process CrIS/ATMS SDRs /EDRS from IDPS

» Generate Matched Measurements of Global RAOBs,  ECMWF and GFS analysis fields

» Process Campaigns of Opportunity (e.g. AEROSE) Data Sets.Post‐Launch Exercises Performed in the Pre‐Launch Phase provide 

adequate know how towardsadequate know‐how towards » Fine‐Tuning of the EDR algorithm using ADL and CrIMSS off‐line

» Evaluation of First‐Light AVTP, AVMP and other EDR Products.

15Validation tools Developed During the Pre‐Launch Helps Post‐Launch 

Processing