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

Re: [gembud] dcshef and dcshef_comet

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: [gembud] dcshef and dcshef_comet
  • Date: Fri, 30 Nov 2007 12:53:28 -0700
Daryl,

The dcshef_comet is the old one written by Peggy Bruehl  that I have
packaged with the distribution for years. I had to rename since NCEP is
now providing their own dcshef along with the OHSHEF library source in
$NAWIPS/extlibs/OHSHEF
(source code release has the directory).  I created pqact entries in
$NAWIPS/ldm/etc/templates/pqact.gempak_decoders for
both decoders, but  both are commented out by default due to the high
load they
tend to generate.

Steve Chiswell
Unidata User Support


On Fri, 2007-11-30 at 13:21 -0600, Daryl Herzmann wrote:
> Good day!
> 
> I recently upgraded a box from GEMPAK 5.10.2 to 5.10.4 and all of my 
> dcshef pqact processes started bombing out with:
> 
> [22855] 071130/1114[FL -1]  Cannot open file 
> /mesonet/data/gempak/coop/YYMMDD_rtp.gem.
> 
> Digging around, I see that dcshef's options are radically different and 
> there is something called 'dcshef_comet' which seems to work like the old 
> dcshef did.
> 
> Did I miss something on the email lists about this?  The "What's New" with 
> GEMPAK 5.10 page has no references to dcshef changes?
> 
> Sorry if I am missing something obvious, thanks!
> 
> daryl
> _______________________________________________
> gembud mailing list
> address@hidden
> For list information or to unsubscribe,  visit: 
> http://www.unidata.ucar.edu/mailing_lists/ 
-- 
Steve Chiswell <address@hidden>
Unidata