AWIPSANC interactions Design Progress to date Remaining work

AWIPS/ANC interactions • Design • Progress to date • Remaining work to be done 1.

AWIPS/ANC interactions design • Performs same as current CIDD system, but on AWIPS. • All human interactions in AWIPS • ASCII XML file two way communications • State of human interactions maintained in AWIPS • Regular updates -- update requests from ANC (data driven) • Human generated updates sent to ANC (human event driven) 2.

AWIPS/ANC communications • ANC: “send me boundaries valid at 2007/11/26 18: 00” • AWIPS: “boundaries at 2007/11/26 18: 00” • 3 boundaries • id=7, lat/lon/u/v sequence = (32. 7, 118. 5, 10, 2), (), . . • id=8, lat/lon u/v sequence = (. . . ), • id=14 sequence = (. . . ) • AWIPS: “new set of boundaries at 2007/11/26 18: 00” • 4 boundaries • Human=TRUE • id=7, lat/lon/u/v sequence = (32. 7, 118. 5, 10, 2), (), . . • id=8, lat/lon u/v sequence = (. . . ) • Id=14 sequence = (. . . ) • Id = 15 sequence = (. . . ) 3.

AWIPS/ANC communications • ANC: “send me boundaries valid at 2007/11/26 18: 06: 00” • AWIPS: “boundaries at 2007/11/26 18: 06: 00” • 4 boundaries • id=7, lat/lon/u/v sequence = (32. 9, 120. 5, 10, 2), (), . . • id=8, lat/lon u/v sequence = (. . . ), • id=14 sequence = (. . . ) 4.

AWIPS/ANC XML • <ANC Boundaries> <Trigger. Time> <Time>2007 -11 -26 T 23: 42: 28</Time> <Utime>1196120548</Utime> <TTime>2007 -11 -26 T 23: 42: 28</TTime> <TUtime>1196120548</TUtime> <Trigger. Type>Boundary</Trigger. Type> </Trigger. Time> <Log>Boundary-- No ascii trigger 25 minutes</Log> </ANC Boundaries> 5.

AWIPS/ANC status • Initial two way capability nearly complete – XML “language” has been specified and designed to by both MDL and NCAR. – Initial implementation nearly one year ago – NCAR implemented an AWIPS simulation capability – Security/firewall issues have slowed us down – Ready to debug and test once these issues are resolved 6.

AWIPS/ANC Status • Testing Phase remains – Need to test every possible sequence of interactions (“Hammer” the system). – Need to test various failure states • Future versions – Installation will likely lead to upgrade requests from forecasters 7.

AWIPS Simulation XML update requests from lonestar XML data to lonestar 8

Lonestar XML update requests to AWIPS sim XML data from AWIPS sim 9

Lonestar XML update requests to AWIPS XML data from AWIPS 10