70 likes | 82 Views
Development of a software suite merging ASPEN's usability with Editsonde's robust processing for dropsonde data, enhancing visualization, data editing, and cross-platform compatibility.
E N D
A Joint Hurricane Testbed (JHT) Project:Development of a unified dropsonde quality assurance and visualization capability • Principal Investigators: • Michael L. Black, NOAA/AOML Hurricane Research Division, Miami, FL • Charlie Martin, Earth Observing Laboratory, NCAR, Boulder, CO • Collaborators: • Paul Flaherty and Jackie Almeida, Aircraft Operations Center, MacDill AFB, FL • Joseph E. Latham, USAFR, 53 Weather Reconnaissance Squadron, • Keesler AFB, Biloxi, MS
Motivation: • Two dropsonde data processing software packages: NCAR’s ASPEN and HRD’s Editsonde- both used operationally and for research data sets • Substantial differences in data output found between the two software suites- caused by variations in operator processing and algorithms • Editsonde has robust data processing capability and extended visualization tools to spot and edit faulty data • ASPEN has advanced GUI for graphics and navigation of user processes and is nearly automatic • Both are computer operating system dependent- ASPEN: Windows, Editsonde: very specific HP UNIX
Project GoalDevelop a single dropsonde processing software suite that: • Combines the ease of use and advanced GUI of ASPEN with some of the more robust processing and visualization capability of Editsonde • Will work on a variety of computer platforms, e.g, Windows, Linux, Unix (including Apple OSX). • Uses standard, flexible, and freely available graphics packages • Provides for different levels of processing: nearly automatic or extended and enhances data editing capabilities • Uses the best-possible data rejection and filtering techniques • Code will be open source allowing users to modify software for specific purposes or for possible improvements
What is the JHT and why we are using this funding source? • The mission of the Joint Hurricane Test Bed is to transfer more rapidly and smoothly new technology, research results, and observational advances of the United States Weather Research Program (USWRP), its sponsoring agencies, the academic community and other groups into improved tropical cyclone analysis and prediction at operational centers. • In this case the operational centers are the NOAA’s National Center for Operational Prediction and the National Hurricane Center • Funds ready-to-be-transitioned research for OPERATIONAL use for one to two year projects
Year One: Approximate Timelines: • Spring and Summer 2009- Define a set of requirements coordinating with TPC, AOC, NCEP, and the AFRC (Wednesday April 29 meeting here at EOL) • Summer 2009- Convert ASPEN graphics to QT graphics • Fall and Winter 2009-2010- Finalize design requirements • Winter 2009-Spring 2010- Design and build a prototype dropsonde QA software package Year Two: • Spring and Summer 2010- Testing and evaluation of the prototype software both on the ground and, where feasible, on the aircraft • Fall and Winter 2010- Refine and modify the software. Complete first draft of a training manual and provide operator training • Spring 2011- Final version of software and training is complete • Winter 2009-Spring 2010- Design and build a prototype dropsonde QA software package
Considerations and Constraints • Time limitations for real-time use on aircraft and level of meteorological training of personnel must be considered • Although enhanced algorithms and data manipulation are desirable for specific research purposes- the operational needs will drive the software development (at least initially) • Complete and efficient training will be needed- both on initial release and ongoing to account for personnel changes • NCAR will be responsible for official version of software- changes have to be approved by an agreement between the JHT point of contact ( J. F. ? )and principle investigators
Some additional thoughts: • Need to find a means for continuing support of software maintenance and modification beyond the 2-year JHT project • Since the software code will be available, a procedure should be established to test, evaluate, and decide on implementation of third party development of new algorithms, techniques, and capabilities • The success of the project will depend on critical feedback from the users within the AVAPS community • Should we consider (at some point) of transmitting the raw D-file for data processing by skilled users on the ground?