1. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas Science Definition Team Activities and the GTWS Draft Data Requirements Jim Yoe, NOAA/NESDIS/ORA James.G.Yoe@noaa.gov Bob Atlas, NASA/GSFC/DAO Atlas@dao.gsfc.nasa.gov

2. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas Overview The SDT and its role wrt GTWS Goals, approach, and actions for 2001 The Product: Draft Data Requirements Initial Applications of Draft Requirements Next Steps

3. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas SDT Role and Composition GTWS joint NASA/NOAA effort “Pre-formulated” as a data buy; to be Useful Achievable (or “doable” in Agencyese Affordable SDT to identify/address science issues NOAA, NASA, and universities represented

4. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas The Process Requirements Workshop February 2001 –SDT plus other scientists, engineers, managers, and industry representatives Input compiled/organized by “Gang of 3” –Atlas, Emmitt, Yoe SDT Meeting in July 2001 Begin reconciliation and consensus process Set up some last minute analysis - RROSSEs Draft Released for Public Comment October 15 2001

5. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas +/- 625 (12)+/- 400 (4)Minimum X-track Regard (km) (Number in () is number of TSVs) 100350Horizontal Resolution (km) (distance between TSVs) 0.5 Horizontal Location Accuracy (km) 25100Horizontal TSV Dimension (km) (maximum for averaging) 0.1 Height Assignment Accuracy (km) 2 0.5 0.25 Not Required 1 0.5 Vertical Target Sample Volume (TSV) Resolution (km) Top of DOR to Tropopause Tropopause to boundary layer top Within boundary layer 0-300-20Depth of Regard (DOR) (km) ObjectiveThresholdGTWS Wind Data Product Requirements

6. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas 2.75 Data Product Latency (hours) 612Temporal Resolution (hours) (revisit period) 100 50 75 50 Maximum Horizontal Speed (m/s) Above boundary layer Within Boundary layer 0.050.1Horizontal Component Bias (m/s) 2 (1.4) 1 (1) 3 (1.2) Accuracy (1  ) LOS Horiz (LOSH) (m/s) Above Boundary Layer Within Boundary Layer (number in () is  S within TSV) 22Number Line of Sight (LOS) perspectives in TSV (angular separation >30 & <150) ObjectiveThresholdRequirement

7. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas GTWSDraft Requirements Requirements to be satisfied taking into account Nominal Cloud Coverage Reference Target Atmospheres Other Requirements Orbital coverage from 80 S to 80 N (min) All raw data to be downlinked Two-year minimum mission life

8. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas Feedback Summary Comments were received –From industry, universities & government agencies Generally positive –Users confident of potential for benefit – Industry instrument builders encouraged that thresholds more achievable than previous –(Lidar) Technological neutrality Specific suggestions –Some objections, recommendations, requests for clarification, and some revision (relaxation)

9. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas Next Steps Public Forum for Comments on Date, venue, and format TBD Follow-up SDT meeting Continued numerical experiments, analysis Consider additional input –DoD requirements beyond current IORD Revise specifications as appropriate

10. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas Next Steps (continued) Develop Validation Plan –Need SDT and TAT to collaborate Complete and publish documentation –Workshop Executive Summary & Minutes –Requirements Crosswalk

11. January 24, 2002 Key West, FL Lidar Winds Working Group Meeting GTWS SDT-Yoe & Atlas Continuing Numerical Experiments NCEP OSSEs –Bracketing OSSEs for forecasts becoming available – Implications NASA/DAO OSSEs –Atlas Described NCAR/NASA NR in July –Now getting first forecast results Full Profiles Everywhere 1 m/s rms errors NH & SH get “twice impact of all other satellite data” “RROSSEs: