[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050719: 20050708: Manual decoding with dcwarn decoder?




Mark,

Good to hear. I probably confused you previously by sending my quick dump of 
the decoder
rather than my actual real-time decoder file naming. 

The dcwtch and dchrcn will be similar, as will dcwou, dcwcn and dcwcp.

It does make for good pictures of Emily.....
http://www.unidata.ucar.edu/content/software/gempak/wseta/index.php?2005071912

Steve Chiswell
Unidata User Support



>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200507192040.j6JKe7jo014770

>Bingo X 2!!!
>
>I was leaving the "_warn" off of the .gem file name, and that was
>preventing gpmap from working it's magic.  Thank you for your wisdom!  
>
>Mark Keehn 
>ITO@HGX
>
>----- Original Message -----
>From: Unidata Support <address@hidden>
>Date: Tuesday, July 19, 2005 2:18 pm
>Subject: 20050719: 20050708: Manual decoding with dcwarn decoder?
>
>> 
>> Mark,
>> 
>> Decode your warning in $GEMDATA/storm/warn/2005071916_warn.gem
>> 
>> This location will match the template for "WARN" found in 
>> $GEMTBL/config/datatype.tbl in the Unidata distribution of GEMPAK.
>> 
>> The two ways to vier the warnings are:
>> 
>> 1) NMAP2, using the "MISC" dataset of "WARN" 
>> 
>> 2) GPMAP, I typically use WARN=last|5;2;3|N|N|Y 
>>   for the map shown at 
>> http://www.unidata.ucar.edu/content/software/gempak/
>> The translation for the above is:
>> last --> use the current system time to plot current warnings
>> 5;2;3 --> use 5 (yellow) for thunderstorm, 2 (red) for tornado, 3 
>> (green) for flood warnings
>> N --> Do not write the start/stop time on the plot
>> N --> do not plot the warning county name (could be lots of 
>> counties in a small area)
>> Y --> Outline the county in the warning
>> 
>> Steve Chiswell
>> Unidata User Support
>> 
>> 
>> 
>> 
>> 
>> >From: address@hidden
>> >Organization: UCAR/Unidata
>> >Keywords: 200507191828.j6JISNjo027519
>> 
>> >Bingo...
>> >
>> >I am now 1/2 of the way to where I need to be.  I removed the
>> >"SATSVRHGX" after the ZCZC and the warning decoded.  I copied the gem
>> >file to $GEMDATA/storm/warn, but now I am having difficulty 
>> getting the
>> >warning to graphically display.  I am using the "gpmap" command, 
>> but the
>> >documentation is a little vague to someone who has never used 
>> Gempak. 
>> >What is the recommended way to generate a display of current 
>> watches and
>> >warnings?  I will eventually be interested in decoding tropical
>> >guidance, but I imagine that it will make more sence once I've 
>> been able
>> >decode and display warnings.  For the time being, I am sending my 
>> output>to an xt, but I will eventually be saving it as GIF images 
>> to be
>> >displayed on teh HGX situational awareness display.  I have also 
>> tried>to display the dummy warning on nmap2, but I have beebn 
>> unsuccessful. 
>> >
>> >Many thanks!
>> >
>> >Mark Keehn
>> >ITO@HGX   
>> >
>> >----- Original Message -----
>> >From: Unidata Support <address@hidden>
>> >Date: Tuesday, July 19, 2005 11:48 am
>> >Subject: 20050719: 20050708: Manual decoding with dcwarn decoder?
>> >
>> >> 
>> >> Mark,
>> >> 
>> >> Just add the ZCZC before the WMO, the pil line will follow the 
>> the 
>> >> WMO and
>> >> is in your bulletin:
>> >> 
>> >> ZCZC
>> >> WUUS54 KHGX 191620
>> >> SVRHGX
>> >> TXC015-473-191700-
>> >> etc.
>> >> NNNN
>> >> 
>> >> I ran this and got:
>> >> % cat WWUS54.txt | dcwarn -v 4 -d - YYYYMMDDHH.gem
>> >> [788691] 050719/1045[DC 3]  Starting up. Version 5.8.3a
>> >> [788691] 050719/1045[DC 2]  read 1054/204799 bytes strt 0 
>> newstrt 1054
>> >> [788691] 050719/1045[DC 2]  read 0/203746 bytes strt 1054 
>> newstrt 1054
>> >> [788691] 050719/1045[DC 5]  Normal termination.
>> >> [788691] 050719/1045[DC 2]  Number of bulletins read and 
>> processed: 1
>> >> [788691] 050719/1045[DC 6]  Shutting down.
>> >> 
>> >> % cat 2005071916.gem
>> >> |SVR|050719/1645|050719/1700||0         
>> >> TXC473    48473 Waller                           TX US     30.01 
>>   
>> >> -96.00      0.00  0  HGX                
>> >> TXC015    48015 Austin                           TX US     29.89 
>>   
>> >> -96.28      0.00  0  HGX 
>> >> 
>> >> 
>> >> Steve Chiswell
>> >> Unidata User Support
>> >> 
>> >> 
>> >> 
>> >> 
>> >> 
>> >> >From: address@hidden
>> >> >Organization: UCAR/Unidata
>> >> >Keywords: 200507191637.j6JGbijo001487
>> >> 
>> >> >This is a multi-part message in MIME format.
>> >> >
>> >> >--Boundary_(ID_0GgC3sUqsuEdFHKVpmcCFw)
>> >> >Content-type: text/plain; charset=us-ascii
>> >> >Content-transfer-encoding: 7BIT
>> >> >Content-disposition: inline
>> >> >
>> >> >Steve,
>> >> >
>> >> >I added "ZCZC SATSVRHGX" to the top, and "NNNN" to the bottom 
>> of my
>> >> >sample severe thunderstorm warning.  When I run dcwarn in 
>> verbose 
>> >> mode,>I get an error stating, "DCWARN -4 Unable to determine 
>> >> bulletin time".
>> >> >
>> >> >I've attached the bulletin that I am attempting to decode along 
>> >> with a
>> >> >segment of the  dcwarn.log file.
>> >> >
>> >> >Please call me at (281)534-5625 x.244 if you think that we can 
>> debug>> >this faster over the phone.
>> >> >
>> >> >I imagine that once I get over the initial hurdle, the rest of the
>> >> >decoding processes should run a little smoother.
>> >> >
>> >> >Thank you!
>> >> >Mark Keehn
>> >> >ITO@HGX 
>> >> >
>> >> >
>> >> >
>> >> >--Boundary_(ID_0GgC3sUqsuEdFHKVpmcCFw)
>> >> >Content-type: application/octet-stream; NAME=dcwarn.log
>> >> >Content-transfer-encoding: base64
>> >> >Content-disposition: attachment; filename=dcwarn.log
>> >> >
>> >> 
>>
>>WzM5NDBdIDA1MDcxOS8xMTIyW0RDIDNdICBTdGFydGluZyB1cC4gVmVyc2lvbiA1LjguMmEK>>
>>WzM5NDBdIDA1MDcxOS8xMTIyW0RDIDJdICByZWFkIDEwNjQvMjA0Nzk5IGJ5dGVzIHN0cnQg
>> >> 
>>
>>MCBuZXdzdHJ0IDEwNjQKWzM5NDBdIDA1MDcxOS8xMTIyW0RDV0FSTiAtNF0gIFVuYWJsZSB0>>
>>byBkZXRlcm1pbmUgYnVsbGV0aW4gdGltZSAgWkNaQyBTQVRTVlJIR1ggV1VVUzU0IEtIR1gg
>> >> 
>>
>>MTkxNjIwIFNWUkhHWCBUWEMwMTUtNDczLTE5MTcwMC0gL08uTkVXLksKWzM5NDBdIDA1MDcx>>
>>OS8xMTIyW0RDIDJdICByZWFkIDAvMjAzNzM2IGJ5dGVzIHN0cnQgMTA2NCBuZXdzdHJ0IDEw
>> >> 
>>
>>NjQKWzM5NDBdIDA1MDcxOS8xMTIyW0RDIDVdICBOb3JtYWwgdGVybWluYXRpb24uClszOTQw>>
>>XSAwNTA3MTkvMTEyMltEQyAyXSAgTnVtYmVyIG9mIGJ1bGxldGlucyByZWFkIGFuZCBwcm9j
>> >> 
>>
>>ZXNzZWQ6IDEKWzM5NDBdIDA1MDcxOS8xMTIyW0RDIDZdICBTaHV0dGluZyBkb3duLgpbMzk0>>
>>M10gMDUwNzE5LzExMjRbREMgM10gIFN0YXJ0aW5nIHVwLiBWZXJzaW9uIDUuOC4yYQpbMzk0
>> >> 
>>
>>M10gMDUwNzE5LzExMjRbREMgMl0gIHJlYWQgMTA2NC8yMDQ3OTkgYnl0ZXMgc3RydCAwIG5l>>
>>d3N0cnQgMTA2NApbMzk0M10gMDUwNzE5LzExMjRbRENXQVJOIC00XSAgVW5hYmxlIHRvIGRl
>> >> 
>>
>>dGVybWluZSBidWxsZXRpbiB0aW1lICBaQ1pDIFNBVFNWUkhHWCBXVVVTNTQgS0hHWCAxOTE2>>
>>MjAgU1ZSSEdYIFRYQzAxNS00NzMtMTkxNzAwLSAvTy5ORVcuSwpbMzk0M10gMDUwNzE5LzEx
>> >> 
>>
>>MjRbREMgMl0gIHJlYWQgMC8yMDM3MzYgYnl0ZXMgc3RydCAxMDY0IG5ld3N0cnQgMTA2NApb>>
>>Mzk0M10gMDUwNzE5LzExMjRbREMgNV0gIE5vcm1hbCB0ZXJtaW5hdGlvbi4KWzM5NDNdIDA1
>> >> 
>>
>>MDcxOS8xMTI0W0RDIDJdICBOdW1iZXIgb2YgYnVsbGV0aW5zIHJlYWQgYW5kIHByb2Nlc3Nl>>
>>ZDogMQpbMzk0M10gMDUwNzE5LzExMjRbREMgNl0gIFNodXR0aW5nIGRvd24uCg==
>> >> >
>> >> >--Boundary_(ID_0GgC3sUqsuEdFHKVpmcCFw)
>> >> >Content-type: text/plain; NAME=WWUS54.txt
>> >> >Content-transfer-encoding: 7BIT
>> >> >Content-disposition: attachment; filename=WWUS54.txt
>> >> >
>> >> >ZCZC SATSVRHGX
>> >> >WUUS54 KHGX 191620
>> >> >SVRHGX
>> >> >TXC015-473-191700-
>> >> >/O.NEW.KHGX.SV.W.0156.050719T1620Z-050719T1700Z/
>> >> >
>> >> >BULLETIN - EAS ACTIVATION REQUESTED
>> >> >SEVERE THUNDERSTORM WARNING
>> >> >NATIONAL WEATHER SERVICE HOUSTON/GALVESTON TX
>> >> >1120 AM CDT TUE JUL 19 2005
>> >> >
>> >> >THE NATIONAL WEATHER SERVICE IN LEAGUE CITY HAS ISSUED A
>> >> >
>> >> >* SEVERE THUNDERSTORM WARNING FOR...
>> >> >  AUSTIN COUNTY IN SOUTHEAST TEXAS
>> >> >  WALLER COUNTY IN SOUTHEAST TEXAS
>> >> >
>> >> >* UNTIL 1200 PM CDT
>> >> >
>> >> >* AT 1114 AM CDT...NATIONAL WEATHER SERVICE DOPPLER RADAR 
>> >> INDICATED A
>> >> >  SEVERE THUNDERSTORM 6 MILES NORTH OF BELLVILLE...MOVING 
>> SOUTHEAST>> >  AT 25 MPH.
>> >> >
>> >> >THIS STORM PRODUCED WIND NEAR 50 MPH IN THE BRENHAM AREA.  
>> EXPECT 
>> >> >WINDS UP TO 60 MPH WITH THIS STORM. 
>> >> >
>> >> >* LOCATIONS IMPACTED INCLUDE...
>> >> >  MONAVILLE...
>> >> >  SEALY...
>> >> >  SAN FELIPE...
>> >> >
>> >> >PLEASE REPORT SEVERE WEATHER TO THE COUNTY SHERIFF...LOCAL 
>> POLICE...>> >OR DEPARTMENT OF PUBLIC SAFETY. THEY WILL RELAY YOUR 
>> REPORT TO THE
>> >> >NATIONAL WEATHER SERVICE.
>> >> >
>> >> >LAT...LON 3010 9616 3008 9627 3005 9617 3008 9614
>> >> >      2989 9591 2970 9617 3006 9647 3009 9637
>> >> >      3009 9619 3012 9617
>> >> >
>> >> >$$
>> >> >
>> >> >NNNN
>> >> >
>> >> >
>> >> >--Boundary_(ID_0GgC3sUqsuEdFHKVpmcCFw)--
>> >> >
>> >> --
>> >>
>>
>>****************************************************************************
>> ><
>> >> Unidata User Support                                    UCAR 
>> >> (303)497-8643                                                  
>> P.O. 
>> >> address@hidden                                   
>> Boulder, 
>> >> -----------------------------------------------------------------
>> ---
>> >> Unidata WWW Service              
>> >> -----------------------------------------------------------------
>> ---
>> >> NOTE: All email exchanges with Unidata User Support are recorded 
>> in 
>> >> theUnidata inquiry tracking system and then made publicly available
>> >> through the web.  If you do not want to have your interactions made
>> >> available in this way, you must let us know in each email you 
>> send 
>> >> to us.
>> >> 
>> >
>> --
>>
>****************************************************************************
><
>> Unidata User Support                                    UCAR 
>> (303)497-8643                                                  P.O. 
>> address@hidden                                   Boulder, 
>> --------------------------------------------------------------------
>> Unidata WWW Service              
>> --------------------------------------------------------------------
>> NOTE: All email exchanges with Unidata User Support are recorded in 
>> theUnidata inquiry tracking system and then made publicly available
>> through the web.  If you do not want to have your interactions made
>> available in this way, you must let us know in each email you send 
>> to us.
>> 
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.