1 / 18

Design Approach Review MDA Completion RPG Build 9.0

Design Approach Review MDA Completion RPG Build 9.0. Brian Klein, RSIS 13 October 2005. Contents. CCR……………………………………………………..………3 Concept of Operations.………………………………….........4 Impacts to Top Level Architecture.......................................5

lamond
Télécharger la présentation

Design Approach Review MDA Completion RPG Build 9.0

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. Design Approach ReviewMDA CompletionRPG Build 9.0 Brian Klein, RSIS 13 October 2005

  2. Contents CCR……………………………………………………..………3 Concept of Operations.………………………………….........4 Impacts to Top Level Architecture.......................................5 Impacts to WSR-88D Architecture…………………………...6 MDA Data Flow……………………..………..........................7 Design Approach ..............................................................10 Products………….....................................................……..12 Development Approach……………………………….….….14 Test Approach…………………………………………..…….15 Integration Challenges/Risks…………………………..……16 Proposed Schedule……………………………………..……17 Action Items……………………………………………..…….18

  3. CCR • CCR • NA05-23001: Complete Transition to the New Mesocyclone Detection Algorithm (Build 9.0) • RC-9375

  4. Concept of Operations • Preparing to transition users to the exclusive use of MDA based Mesocyclone data • Alerting/UAM Product • Alert Timing: End of Volume • Alert Threshold Values: 1, 2, 3, 4, 5, 6 (Strength Rank, AWIPS default value: 5) • Default Paired Product: MD (141). • Combined Attributes Table (CR/CZ, 35-38; CRE/CZE, 95-98) • RCM Product (74) • Based on Minimum Display Filter Rank (default 5) • Begin central collection of MD product (141) after Build 8 deployment • Eventual removal of the legacy algorithm including the M and MRU products (proposed for Build 10)

  5. Impacts to Top-Level Architecture • External Display Systems • AWIPS software may be affected by new alert category • Possible SCAN software modifications required if parsing of Combined Attributes Table or SCAN use of WSR-88D alerting functionality • Users of RCM, UAM, CR/CZ and CRE/CZE (only the Combined Attributes table) may be affected in Build 9 • Users of M and MRU should plan to transition to MDA products (MD, DMD) prior to planned removal of legacy algorithm in Build 10. • Benefits • Remove redundant processing • Remove possibly conflicting mesocyclone information • Early transition to MDA will decrease risk of legacy removal

  6. Impacts to WSR-88D Architecture • Product Sizes • Unchanged • New API • None known • CPU • Unchanged • Memory • Unchanged

  7. Design Approach • Add new Alert Code and Threshold in both the Volume and Forecast alert groups, retaining those for the legacy Meso alert until its removal in Build 10. • Increment version number for products containing Combined Attributes Table (CR/CZ (35-38); CRE/CZE (95-98) • Change the RCM product to report MDA features that meet the minimum display rank threshold: /NMES03: M05ABC M05DEF M06GHI • Change the Combined Attribute table in the CZ product: • MDL requests version change

  8. Design Approach (cont’d) • UAM Product ALERT AREA # 1 AZIMUTH 278.9 DEG RANGE 22.1 NM ALERT CATEGORY MDA THRESHOLD 5 EXCEEDING VALUE 6 STORM ID I0 STORM MOTION 216/ 55 DEG/KTS

  9. Products MD PSB & GAB(unchanged in Build 9) • Mesocyclone Detection (MD, 141)

  10. Products (cont’d)MD TAB (unchanged in Build 9)

  11. Development Approach • ANSI C conforming to RPG Coding Guidelines. • Develop and test with Build 8v1 on dev3 Blade with connectivity to AWIPS lite. • Test on a Linux platform. • Coordinate product changes with FSL and MDL by providing samples for their testing.

  12. Test Approach • cvt display of UAM and RCM as stand-alone alphanumeric products • AWIPS lite display of UAM and RCM using D2D text window. • cvg display of CR and CRE products. • AWIPS lite display of Combined Attributes Table in D2D window. • Test Cases: • Full Load, 21 April 1996 • No special test cases required.

  13. Integration Challenges/Risks • RPG Risk Very Low • No change to CPU utilization, memory use or product sizes. • External User Risk Low • UAM: Same format, new alert type • RCM: Same format, new Part C content. • CR/CZ, CRE/CZE: Same format, new GAB content. • Version number change has caused unexpected impact in the past. • How to treat “low core” and “shallow” features? • Linux platform testing challenge.

  14. Proposed Schedule Summary(as of 10/02/05)

  15. Action Items _______________________________ _______________________________ _______________________________ _______________________________ _______________________________

More Related